groups specification - amazon web services · 2015-10-07 · groups specification funtional...

GROUPS SPECIFICATION

FUNTIONAL REQUIREMENTS AND SPECIFICATION FOR V1.5 OF THE CURRIKI

WEB SITE- THE “GROUPS FOUNDATION” RELEASE

Version Date Author Description .1 8/13/2007 Joshua Marks Draft - outline level .2 8/29/2007 Joshua Marks Draft outline and Use case classes .3 9/13/2007 Joshua Marks Complete rough draft with first wireframes .4 10/01/2007 Full Team Revised scope and reworked elements .5 10/15/2007 Full Team Full revised wireframes and first draft

treatments .6 10/21/2007 Full Team Revised treatments and full edit pass on all

tabs .7 10/30/2007 Full team List of final elements and refinements

needed, updated wireframes. .8 10/31/2007 Joshua Marks Compile and reformatted into final draft. .9 11/01/2007 Joshua Marks Complete compiling and re-formatting.

Some final treatments pending as well as New My Curriki section.

1.0 11/8/07 Joshua Marks Insert final design treatments.

Curriki V1.5 Groups Foundation Specification Page #2

TABLE OF CONTENTS Overview............................................................................................................................................................. 3 Use Cases and User Stories by User Class .................................................................................................... 4

User Class 1- Group Administrators (Project leaders) ........................................................................ 4 User Class 2- Group Members (Including Project Leaders)............................................................... 6 User Class 3- Curriki Members (Including Visitors, but visitors must first join Curriki before they can join a group) ........................................................................................................................................ 9

Creating, Finding and joining groups........................................................................................................... 10 Group Info Header ................................................................................................................................. 10 Browse Groups ........................................................................................................................................ 11

Browse Groups Listing Page ................................................................................................................. 13 Creating a group....................................................................................................................................... 14

Create new Group Jump Page ............................................................................................................... 14 The Create New Group Form............................................................................................................... 14 Complete Creating Group Interstichel Page............................................................................................ 16 Welcome Group Admin e-mail.............................................................................................................. 16

The Group Home Page/Tab......................................................................................................................... 16 Description of parts of Group Home and group area: .................................................................................... 18

Becoming a Group Member of an existing group ..................................................................................... 24 The Messages (PLOG in future releases) Tab............................................................................................ 29

Message Tab elements: .................................................................................................................................. 31 Notifications by e-mail in Messaging: ............................................................................................................ 32 Viewing (Reading) a Message....................................................................................................................... 32 Create Edit Message..................................................................................................................................... 35

The Curriculum Tab ....................................................................................................................................... 37 Elements of the Group Curriculum Tab: ...................................................................................................... 39 The Group View All Contributions sub-page of the Group Curriculum Page ............................................... 40 Elements of the Group Contributions table: .................................................................................................. 41 The Search Group Resources sub-page of the Group Curriculum Page ........................................................... 42

The Members Tab ........................................................................................................................................... 43 Elements of the Group Members tab:............................................................................................................ 45

The Documentation Tab................................................................................................................................ 46 Elements of the Group Documents Tab ........................................................................................................ 48

The New My Curriki....................................................................................................................................... 49


Groups Foundation Specification FUNTIONAL SPECIFICATION FOR V1.5 RELEASE OF CURRIKI

OVERVIEW

There are a large number of user stories involved in groups and courses as described in the original GELC TDD document. It will not be possible to implement all of the parts of the full groups and courses vision in this initial R3 (V1.5) Groups’ release (“Groups Foundation Release”). However, the intent is provide both sufficient utility to meet the early adopter’s basic requirements for collaboration tools, and provide the technical and data model underpinnings necessary to enable extension to the full elaborated vision.

To help organize the many use cases and user stores listed here, they have been divided into classes by user type (Actors): Group Administrator, Group Member, and Visitors & Curriki Members. Within each user class, user stories are listed in functional order and identified as targeted for inclusion in the pending Foundation Release (V1.5) or for future enhancement and extension iterations of the groups’ implementation.

The general technical strategy is to selectively use, integrate and extend the elements of the Chronopolys systems (Accessible at http://curriki.chronopolys.net with provided user account). However, in consideration of the needs of the Curriki user, the presentation and UI elements of the Chronopolys system have not been used “AS IS” due to the design requirements of simplicity and ease of use. Initially, only a small sub-set of the Chronopolys functionality will (may) be integrated into the Curriki application and those elements modified or extended to meet the requirements of the initial set of user stories. There are other new elements not provided by Chronopolys for group collections and for future releases. The intent is to extend upon the shared underlings and integrate other Chronopolys interfaces and features (such as tasks and events) and Curriki features (group templates and frameworks) as Curriki users request such extensions and in continuing short cycle design/development iterations. However, it is quite possible that after the design process and full technical review is completed that it would be more efficient for the development team to create the needed functionality on top of the XWiki core features and APIs rather then attempt to overly modify the Chronopolys interface (Which also sits atop the same XWiki APIs). This will be clarified in the development plan.

This functional requirements document contains the primary screens in full elaborated treatments along with a narrative descriptions of the functional behavior of each element. The document is to be used to develop the site functionality, and during development, as questions or functional details are needed, they should be added to this document. Some specific elements of the high level design will require their own detailed design documents or refinements to existing functionality, and those have been identified below. This requirements and design document will be a living document and will be used as a road-map for prioritizing and sequencing then defining future feature enhancements and refinement projects related to groups.

http://curriki.chronopolys.net/


USE CASES AND USER STORIES BY USER CLASS

USER CLASS 1- GROUP ADMINISTRATORS (PROJECT LEADERS)

Group Administrators are Curriki members who either create (Sponsor, propose) a new project group or assume group administration responsibilities for an existing group. They have the ability to manage the membership, roles, project area configuration, group process, procedures and policies. A group can have one or many administrators. Use cases related to the Project leader include:

1. Create a new group/project and associated metadata or edit an existing one – Perform all the initial set-up and configuration of a group/project including:

a. Create/Edit Group title/name (Which becomes a Curriki sub-domain to direct link to the group home page e.g. http://groupname.curriki.org)

b. Create/edit Group Description (Text/HTML/Wiki block that is used wherever projects are listed or linked- The group equivalent of a resource description.)

c. Upload or change group logo d. Set/edit group membership policies (Open membership or Closed

Membership [By Request/Invitation]) e. Set/edit group subject(s) and educational level(s) (Classify group by

Curriki master framework and educational level metadata just like assets.)

f. Set group license policy (Pick default for group assets and collections)

g. Set Default Access Rights h. (Desired, not required) Set Project/Group status (Proposal, In

Development, Active, Complete, Revised, Retired- This vocabulary needs review. May be redundant with project phases.) – Default to proposal when created.

i. (Not Needed until requested) Configure what elements are present on the group home page

i. For visitors ii. For Members

j. (Future Release- Part of future Project Tab) Create/Edit Group Charter and other group organizational documents (Pedagogy, Methodology, Policies and Procedure, Bi-Laws, Style Guide, etc.- Each canned Wiki pages in a default group home page)

k. (Desired) Close (Retire) group/project- (Does not delete, but becomes inactive)

i. Adopt an inactive group (Become leader) l. (Future Release) Create group/project type – Review Group,

Curriculum Development Group, Project Group, Text Book, (We might extend this list)

http://groupname.curriki.org/


2. (Future Release- In Project Tab) Create and Manage Project Phases or Milestone and schedule- set which phase is active

a. Create/Edit Phase or Milestone b. Set start date and target end date c. Set phase as active or inactive d. Set percentage complete for phase (Enhancement)

3. Manage members a. Approve Membership requests (Nominations)- For closed groups,

requests for membership (Both replies to initiations and unsolicited requests) see list of nominees, and approve or reject (With requisite welcome or sorry explanation automated e-mail).

b. Remove Member and edit member’s group settings- With e-mail explanation/notification.

c. Give a group member a leader admin rights (Need to think about revoking rights, might be Curriki admin only)

d. Assign group members to a functional role beyond Admin (Default roles might include Leader, Teacher, Editor, Contributor, Developer, Reviewer, and possibly Student- Need to review)

e. (Future Extension) define custom roles within a group 4. (Future Extension) Create Group Template (In Collections Tab)

a. Create a template (Private) b. Publish/Un-publish the template to the group. c. Edit a template or its metadata

5. Manage Plog/Messages a. Edit or Delete any Message entry (Plog entry when adding tasks and

events) b. (Future Extension) Select Messages (Plog articles) to be featured in

group home page. c. (Future Extension when Tasks implemented) View completed tasks

or events d. (Future Extension when Tasks implemented) Sort tasks or events by

start date, due date or completion percent (Task only). e. (Future Extension when Tasks implemented) View tasks that are

“Checked-out” 6. Manage Group Collections (aka Course Components)

a. Create, Add, Edit, Delete Group Collections and Assets b. Delete or edit any comments on group Assets c. Set Access Rights in rights for group assets (Open- Public view or

edit, Protected- Public view only/group members edit, Private- Group Members only view and edit.)

i. At Group level as default when creating group, ii. At Collection/folder (Composite asset) level in CB or when

creating, 1. (Need to discuss) Option to have the change set for all

sub-assets, with confirmation (Very-Desired) iii. At Asset level in the CB


d. (Future Extension) Set production status for assets and collections (WIP, Draft, under review, reviewed, under revision, revised, final, retired- Vocab needs revision)

i. Have option to have status changes for collections and composite assets “Cascade” to sub-assets (Also Very Desired)

ii. (Desired) Create a Published Rendition of a component (Exported into a group published assets space like PubColl_Groupname as a public version.)

e. (Future Extension)- Create Collection style sheet 7. (Future Extension) Create and edit Course/Group Framework, managed in

project tab, and added to alternate alignments. When adding to a group collection this framework, not the master framework, is presented and the master framework alignment I inferred from the group subject alignment.

8. (Future Feature) Create custom group skins and style sheets.

USER CLASS 2- GROUP MEMBERS (INCLUDING PROJECT LEADERS)

Project members are contributors and collaborators who together or under the direction or within the group policies set-up by the Group Administrators. Administrators can do anything Members can do, but Members can not do the Admin specific uses above. All group members and Administrators can:

9. Join and manage their Group membership profile a. Complete the group member set-up up form

i. Opt out of e-mail notifications form the group ii. Create Group member profile (IN addition to there general

Curriki profile)- Used to describe your view of your place in the group.

iii. Remove yourself form a group (Unless you are the last project leader for that group in which case you must assign another group leader before removing. To be discussed further.)

iv. (Potential Future Feature) Agree to any terms and policies of the group.

v. If a closed group, the membership form is sent to the project leader(s) for approval. It is up to the project leaders to send a welcome note or rejection note.

vi. View list of group members and their group profiles. vii. Invite Members

1. (Extension) Find/search for members (By Subject, Level and Search string.)

2. Send e-mail to existing Curriki member inviting to join the group (Enter either screen name or e-mail address)

3. Send e-mail to non-Curriki member inviting them to join the group and Curriki (Enter e-mail address for a non-Curriki member)


viii. Select Role(s) in group (Other then Group Admin)

10. Interface with Message Plog- (Project Log) and group home page elements: a. Create and edit a Message

i. To individual group member(s) ii. To the entire group

iii. To Role(s) in group iv. Attach files to a message v. Add comment to message

vi. Optionally send message via e-mail (Notify – Select check box)

b. (Future Extension) Create and edit an event i. When creating new event, optionally set "send notification of

new event or event change" ii. Edit event content (Including start date/time, end date/time,

location and body) iii. Invite members to an event (Including entire group) iv. Add attachments to an event v. Add a comment to an event

vi. Set you attendance value for an event (“I will be there:, “No Answer” and “Will not be there”)

c. (Future Extension) Create or edit a Task i. When creating or editing a task, optionally set ‘send e-mail

notification’ of new task or task change ii. Open (To all group members as a request)

iii. Add or remove specific group member(s) (Including yourself) iv. To Role (Enhancement) v. Set due date

vi. Add comment vii. Add attachment

viii. Add a Group asset link (attachment) to a Task ix. Set percent complete (Only if you have it checked out/active) x. Set status (Pending/Request, Checked-out/Active, completed)

d. (Future Extension) View events/meetings chronologically i. All events that are pending

ii. Just events that include user and are yet to end (Include ones to entire group)

iii. Passed events e. View Messages

i. All messages Chronologically ii. Message that include user (Include or exclude ones to the

entire group) (My Messages) iii. Message the include user’s role in group

f. (Future Extension) View Tasks i. All tasks chronologically by start date


ii. All tasks chronologically by finish date iii. All tasks that include (Are assigned to) the user or their role

(Include or exclude Open tasks) (“My Tasks”) iv. All tasks that user has checked out (“My active tasks”) v. All Completes tasks (Or tasks sorted by status active, pending,

completed) 11. Edit Collection/Component in group collection

a. View or Edit an existing asset (If rights allow)- Including Metadata and History

i. User can not edit license or rights holder (Only Group Administrators can).

b. Add/create an asset into a collection/component (If rights allow) – Adding assets to a group collection, even if they are existing assets in the repository will create a new asset in the group collection space (Copy if needed.)

i. The original contributor (Creator) is the owner of the asset, but the group is as well (e.g. both the group leader and the creator can edit rights and license).

ii. The one exception is adding an ‘ND’ licensed asset to a group collection in which case it is a pointer and not a copy. (perhaps we should discuss this further?)

iii. (Future feature when group templates are implemented) When creating an asset/resource from a template, any and all group templates appear and are listed on the top of the list of available templates in the select template dialog.

c. Comment on an asset or collection/component i. Edit or delete their own comment, but not others’ comments.

(This should be global) d. (Feature with Tasks or after) Add a task to an asset (Source or

composite) – When as task is added to an asset, it appears in the tasks tab in the CB (Or perhaps as a marker in the display in the edit tab? Or both. Basically the same as comments.) Tasks also appear in the PLOG. Tasks added to assets in the group collection include a link to the asset it is associated with.

i. Assign to self ii. Assign to group member(s)

iii. Assign to group role (Extension) 12. (Group documents tab feature under consideration) View and work with

group Wiki pages including (For discussion- Some canned pages): i. View Group Bylaws (No editing except for project leader)

ii. View Group Policies (No editing except for project leader- Must be agreed to during membership)

iii. View and edit course/project pedagogy iv. View and edit course methodology v. View, Create and edit style sheets and style guides

vi. View, create and edit there topical wiki pages for the group.


13. Implements MyCurriki tabbed interface.- Interact with and navigate to a. My Profile (See your view and in addition, visitors view- desired) b. My Collections, c. My Contributions, d. My Blogs, e. My Groups,

i. My Messages, ii. (Future Feature) My Tasks,

iii. (Future Feature) My Events f. Impalement personal message/mail feature (Desired Future Feature –

like a group message, but person to person outside of groups context) USER CLASS 3- CURRIKI MEMBERS (INCLUDING VISITORS, BUT VISITORS

MUST FIRST JOIN CURRIKI BEFORE THEY CAN JOIN A GROUP)

Curriki members can join as many groups as they like, or none at all. Curriki members are known by their display name and their profile image (Avatar). Curriki Members must have validated e-mail addresses (By responding to an email to validate their account- See user ID and Validation spec). Members will discover groups by discovering content in the repository that belongs to a group collection (The group name links to the Group Home Page), by finding users who belong to groups, by being invited to groups, or by browsing groups by topic.

14. (Future feature) Search for users and groups- Search interface with optional query string and with topic and level filters.

15. Browse groups by subject, or All Groups a. See list with group logo, description, which links the Group Home

Page 16. View a Group Home Page (Form any link with the group name or logo)

a. As a non-member, you can not edit or add anything to the to the group home page

b. For open groups, there is a Join group button on the group home page c. For closed Group, the join button says “Request membership” d. Visitors can only see the home page and the collections tab, they can

not see the other tabs (They are Greyed out or contain just a message like “You must be a group member to view this page.”) assume they can see collections tab only if the collections are public -Jennifer Lytle 9/28/07 1:50 PM

17. Choose to join (Or request membership)- (Note: A user who receives an invitation to join uses another link to the join/request membership form.)

a. Closed group- The form finishes with an acknowledgement e-mail and a notification to the project leader(s) to approve or reject the request.

b. If the user receives an invitation to join from an existing group member, they fill out the same form (From a link in the


email/message), but they are taken to a version that gives hem immediate membership

18. View and edit the group resource only if rights allow a. Visitors can not edit anything, or comment b. Curriki members can comment on any asset they can view, and edit

any open assets. 19. There is one special case which is a visitor (Non Curriki members) gets an

invitation to join a group. In this case the message contains two links, first to Join Curriki as a member, and a 2nd to join the group.

CREATING, FINDING AND JOINING GROUPS

The point of entry into a group is the Group Home page. The group home page is accessed from its own sub-domain (e.g. http://groupURL.curriki.org) and form any display of the group name, logo or ‘Masthead’. The group name appears just like, and in place of the contributing user name in all search pages. However, in the asset view metadata header- Both the creator and the group are presented for assets that belong to group collections.

GROUP INFO HEADER

Figure 1- Groups attribution in view info header

http://groupurl.curriki.org/


Group Logo- Links to the group home page

“From” Attribution- lists the display name of the group who’s collection space this asset lives in.

Created Attribution- The Creator/Contributor’s display name is displayed and links to their MyCurriki page.

Figure 2- Warping of text in info header attribution area

If the group or contributor’s display name is wider then the text area (Bounded on the right by the next table column containing “Last Updated”) then it wraps to the next line down. If the text string is to long and there are no spaces before the wrap point, then it truncated. This is the generalized wrapping rule for titles, names and descriptions.

BROWSE GROUPS

From the updated left Navigation bar, users will have new options. Under the My Curriki section, users can navigate to the new “My Groups” section of their nor re-formatted My Curriki page. Under the Member Community section, in addition to Members Hone page, Volunteer and Featured Members links, members and visitors will be able to view featured groups, browse groups by topic, browse all groups, and optionally (At editorial discretion) a link to create a new group. The "Browse group" features are essentially the same as browsing resource by topic, but instead is browsing groups by topic, using the same "Card" interface but resulting in a list that includes the groups "Masthead"- which is their logo and description in a display box:


Figure 3- Browse Groups and Left Nav

This interface is the same as with browse resources by subject, but the images may be a bit different. If the user selects a category, or “All Groups,” a listing page of group mastheads, arranged alphabetically, is displayed. If there are more then 20 (System configurable number) of item on the list, then the standard paging mechanism used in search should be added to the bottom on the listing page.


Figure 4- Browse groups by category listing page

BROWSE GROUPS LISTING PAGE

In the browse groups listing page you find a sequence of Group Mastheads containing the logo (Or a default logo if none is added) and the group description. The logo and the title bar link to the group home page for that group. (Note: 5W to provide exact logo size and masthead design and layout details in the Curriki Style Book.) The group Masthead should be a re-usable style macro that takes a group name as input, in this way editorial can create feature pages and articles that contain group mastheads.

The primary way to find groups should be by browsing groups or feature pages, but will also discover groups of interest form content in the repository, from their or other member’s MyCurriki pages, and from being invited to join a group via an e-mail. Regardless of where a user comes from, all roads link to the Group Home Page. Essentially the group home page acts as the “My Curriki” page for the group. However, the group home page does not exist until some member creates (Charters, Proposes, or Sponsors) it by selecting “Create new group.”


CREATING A GROUP

There are two ways a member can start a group (Neither is accessible to visitors). From the Browse Group page (See Fig 3 above) and form the Member’s Home page, there is a new button “Create Group” to be placed by editorial:

Figure 5- Create New Group Button

When a user selects “Create New Group” they are taken to the “Create a new Curriki Group” jump page. This should be a interstitial “About creating groups” info page helping folks understand what a group is what it means to make on. From this jump page, the next button the presents the actually create new group from. A user must have a validated e-mail address to create a group, if a user who has not validated their e-mail attempts to create a group, the are re-directed to the validate page. (See validation and Send to a Friend spec)

CREATE NEW GROUP JUMP PAGE

See [Create New Group: Jump Page Mock-Up] in Copy for Groups Document.

THE CREATE NEW GROUP FORM

After the user selects to actually create a group from the jump page, they are presented the create group from where they enter all the required elements for a group. When submitting this form, each element is required and for those that do not have defaults (Title, Description, Subject and level- the others have default values) a completeness check is done and any field not entered are highlighted to be completed (Much like the user registration form.)

For exact copy see the [Create Group From] in Copy for Groups Document.

The data elements of this form include:

Group display Name – Limited to 64 characters. Used as the display name for the group globally

Group description – a text block (Accepts HTML and Wiki syntax for buttons etc.)

Sub-domain and group ID/Space name - This is no more then 32 characters with no spaces or special characters. It is also not case sensitive. There will be a list of sub domains we will not allow (Mail, Doc, RSS, Beta, Demo, Dev, etc. – Need full list and the ability to move a group if necessary). This mist also be uniqe, so if another group has this name, the user is asked to change it.

Set Membership Policy – (Open or closed- default Open)

Set Language – Same as asset language list.

Set Group Licenses Policy – Same as asset license, and used as the default when creating new group collections.

Set Default Access Privileges – Similar to asset access privileges, except “Protected” means not editable by non group members, and Private means no viable by non-group members.


Figure 6- Create Group From


When the Group Creator submits the correctly completed form, the group home page is created and the user (Group Admin) is taken to the group’s home page. The system also e-mails a confirmation to the Group Admin with links to their group home page and basic directions for project leadership. Also the e-mail should be sent regardless of the user's opt-out setting for unsolicited e-mail. (This e-mail is solicited.) Upon creation of the group, the system generates a sub-domain for quick access to the group home page (http://groupURL.curriki.org.). This information is included in the create group confirmation e-mail.

Group Admins are automatically added as members to the group and are given the ‘Group Admin” role in that group. When a Curriki member accepts the Admin role for a group, they are added as members of the “Curriki Group Administrators’ Group”. This is a group managed by Curriki and intended to support, direct and communicate with Group Administrators/Leaders across Curriki.

COMPLETE CREATING GROUP INTERSTICHEL PAGE

When the Group is first created, the Group Administrator/creator is taken to the project home page, where they can continue to configure the group. The first time the creator visits the page, a “How to set-up and configure your group” message/dialog is presented. This one time information page should instruct the administrator to upload an image for the logo, and create a welcome message and generally get the new group administrator acclimatized to the group features and what the admin can/should do.

See [Interstitial Dialog Mock-Up: Occurs Between Create a Group Form Submit and Launching of New Group Space] in Copy for Groups Document.

WELCOME GROUP ADMIN E-MAIL

See [Welcome Group Admin, thank you for creating group e-mail] in Copy for Groups Document.

After closing the interstitial message, the new group admin is taken to the group are and the group home page tab.

THE GROUP HOME PAGE/TAB

The Group Home Page is the landing page, or Front Door, for a group. It is presented differently for group administrators, group members and visitors. Visitors to closed groups have more restricted access. Members and group administrators see and can access all the tabs a links on the home page. Visitors to closed group, however, can only see the home page and the group’s “Collections” (Curriculum) tab. For visitors to a closed group, links to other arts of the group area are not active (Or take the user to a “You must be a member” message). Group administrators, additionally, can edit some elements of the home page. The following is the Group administrators view of the group home page. The edit links would not display for group members or visitors.

For exact copy and translations strings for the elements of the group home page please see [Group Home Tab] in Copy for Groups Document.

http://groupurl.curriki.org/


Figure 7- Group home page, Admin view

DESCRIPTION OF PARTS OF GROUP HOME AND GROUP AREA:

1) Breadcrumb – The group home page and all sub pages of a group area are listed in the breadcrumb (e.g. “This group > Tab in this group” for for the home tab above "This Group> Home", and there are also sub-ages of tabs like “This Group> Home > Edit Mastead”)

2) Group title banner – The element between the breadcrumb and the group area tabs is persistent as long as you are ins a group tab or sub-page. This “Anchors” you to indicate that everything you are looking at related to the specific group (Even though the same info is in the breadcrumb.)

3) Group Feature Tabs - Presents the appropriate group page when a tab is selected. For group members all tabs are available. If the group is an open group, then visitor also see and can view all tabs. However if the group is a closed group and the user is not a group member, only the Group Home tab and Group Collections tab are available. The rest are visible but "greyed-out" and can not be selected for visitors in closed groups.

4) Group Home Tab Element 1- About Group Block or “Masthead.” This is the description and Logo for the group. The logo can be uploaded or updated by a group admin (Just like personal profile), and the description can be edited by clicking the edit button on the section title bar. Only Group Administrators and System Administrators see this edit button. This edit button takes the user to the edit group masthead page.


Figure 8- Edit Group Masthead

4.1) In the edit Group Masthead sub-screen, the user can update the title, description or logo image for the group (The Masthead). The Submit Updates saves any changes, and cancel return to the Group Home page. Cancel also returns to the group home page, but without saving changes. Notice that the breadcrumb (Group Title > Home > Edit Group Masthead) indicates this sub-page relationship with home. (Note, if there is an issue with loosing changes to the title or description when uploading a new image, provide a warning.)

5) Group Home Element 2- Group Home page welcome message. This is a pure wiki page that can be created or edited only by a group administrator (The edit button does not show for regular group members or visitors). If the (a) group admin has not edit edited (Created) a group welcome message, members and visitors do not see this element, but group admins see it with a default message saying, "Create home page welcome message for visitors and members" (See [Copy for Group Home Tab] in Copy for Groups Document for details) with a button to move to the edit interface (Which is the same as for Wiki pages in the documentation tab- See the description of the Edit Wiki Page interface in the description of the Documentation tab below). There is only one home page welcome message element, intended to communicate the high level status and pending activities to the group. It is an optional element and can be as long as the group admin likes. When a Group administrator selects to edit the Welcome message they see the following:


Figure 9- Edit group Welcome Message

6) Group Home Element 3- The Recent Changes section. This area will show updates to the group messages, membership and collections. If the group is an open group, then everyone sees this element. However, if it is a closed group, then only group members see this element, visitors do not see this element. It is automatically generated and shows the last "N" (N- a system configurable number initially 5 or 10) events in the group. It is an RSS feed display for the group, and includes an RSS icon link to the actually XML RSS feed so people can subscribe to the group RSS feed. Each feed record contains the change information, a link to what was change and who changed it plus a short event message. The complete list of events types that appear here includes:

6.1) Member chance (Add member, edit member, remove member) 6.2) Message change (Add message, edit message, delete message) 6.3) Resource change (Add resource, edit resource, delete resource) 6.4) Document change (Wiki page or document added, wiki page or document edited, wiki page or document deleted)

Each entry in the event log includes the following:

6.5) Date and time of change (And how long ago if in the last 24 hours.) 6.6) Event log message (From the list above). If a message, document or resource was added

or edited, it is listed by title, and the title links to that resource, message, wiki page or document. If a user is added or edited, then the message links to that user's My Curriki profile. For exact wording of all event messages, please see [Activity Descriptions] in the Copy for Groups Document.


7) Group Home Element 4: Group Information- This displays all the settings for the group to both members and visitors including:

• Member Policy (Open or Closed)

• Default license for group assets and collections

• Default Access privileges for resource (Opens, Protected, Private to group or Restricted to individuals/roles)

• Language

• Subject(s)

• Educational Level(s)

• Start (Creation) date

Only group admins can edit this element and only they see the edit button. When the edit button is clicked, the Edit Group Info from is presented (See below). Submitting edits to this form or canceling returns the user (Admin) to the group home page.


Figure 10- Edit group Info Form


8) Group Home Element 5- Search Group Assets and Resources- This takes the user to the Search Group Contributions page (See below under Collecitons/Curriculum Tab) which is essentially the advanced search results page under the contributions tab, and set to only match against group resources and collections. This element is available to group members and visitors regardless of whether it is an open or closed group. However, only group members should see matching results for “Private” group assets. Using this takes you to the Search Group Resources results page under the Curriculum Tab.

9) Home Page Element 6- Membership Info Block- This element is used to generate new members from both visitors. What is presented depends on both the group membership policy and the status of the person viewing the page. The following matrix describes what happens in each of the six combinations.

Open Group Closed Group

Visitor (Join this group) is the

action- Goes to Join Group Form (See below)

(Request Membership) is the action - Goes to Request Membership From (See Below)

Member (Invite Member) is the

action - Goes to Invite Member form (See below)

(Invite Member) is the action - Goes to Invite Member form (See below)

Group Admin (Invite Member) is the

action - Goes to Invite Member form (See below)

(Invite Member) is the action - Goes to Invite Member form (See below)

Table 1- Modes of the Membership Block

This area of the Members Home page functions differently for Visitors and Group Members. In total, there are 3 different modes of this element (Join, Request, and Invite) (A four "Nominate" state has been removed). Each mode has its own descriptive paragraph and a different action button.

Visitors see a message on how to become a member. There are two sub cases- If the group is “Open” policy the button says “Join Group”. If the group is Closed Membership, the button says “Request membership”. After submitting the form the user gets a message of welcome to the group (If open), or “Your request to join has been set to the group leader(s) and you will be informed when your request has been reviewed and approved.” In the case of a closed group, the Project Leader(s) are notified of a new request, and a pending member is added to the member request/nominate queue. The details of this are described in the flow charts below.

Members and Admins see a button that says “Invite new members to Join”. In this form, members can enter either a Curriki user ID or an e-mail address. The system checks if the user ID or e-mail address is an active Curriki member and if so sends an email inviting them to the group and describing how to become a member and includes a link to the join/request membership form and the group description. However, if the user name is not in the DB or the e-mail address is mal-


formed, then an error is presented. If, lastly, the e-mail address is well-formed but the address is not a Curriki member, then a slightly different message invites the person to Join Curriki and then join the group with links to the Join Curriki page and the Join group form. Again, details on this flow are depicted below.

Before a member can join a group, their e-mail address needs to be validated. If a member who's e-mail has not been validated clicks on the join link, then they are taken to the Validate member e-mail form

Only signed-in members can join a group. e.g. if the join or request membership button is selected by a visitor, they are taken to the log-in or register page.

BECOMING A GROUP MEMBER OF AN EXISTING GROUP

There are several path a user can take to become a member of a group. All of them lead to a membership from (Either Join if an open group or Request Membership if a closed group.) A user can get here from the group home page, or from an invitation e-mail they may have received from an existing group member. The following flow charts describe the process from the point of selecting to join or request membership.

Both the Join and Request flow, and the related Invite flow generate notification and incite e-mails. The exact copy of these e-mails and for the related dialog boxes and error messages can be found in the Copy for Groups Document. (Jennifer to make sure all messages and errors are covered)

Figure 11- Request Membership Form


Figure 12- Join Group Flow Chart


Figure 13- Request Membership


There are two setting a user selected for then group membership, and both are defaulted to yes-

1) "Allow e-mail notifications from the group" - Regardless of the users opt-out setting for Curriki unsolicited e-mail, the user can opt-in or out of receiving e-mail notifications when a group member creates a message and chooses to send a notification (See below in Messages)

2) "Notify me when any asset, message or document I made in the group is changed" - This setting will send a notification to the user when anything they create in the group is modified. This notification contains the same event as appears in the recent events area of the home page, and is sent form "Curriki notifications".

There are also two optional fields in the group membership profile:

1) The member statement or Group Member Bio- A free text area (Including HTML) for the user to present info about themselves to other group members.

2) Select a Role in the group - Initially the group role list will be limited and set by Curriki editorial. Editorial should be able to extend and modify this list at any time. One role in the group is Group Admin, but only group admins can select this value, it does not appear for members or prospective members as an option (Note: The Data model should support future extension to have each group have its on list of roles, and that that be editable by the group administrator(s)). Role lists should be internationalizable so the display name for a role can be changed and localized without changing its stored value. (If we can add the ability for the group admin to customize the group role list in the edit group info form, that would be extremely highly desired.)

Current proposed roles list includes: Leader

--this is the person who made the group --this is someone designated to lead any other admins designated in the future --this person should lead by being proactive in building/maintaining all areas of the group --this person is concerned with defining best practices for the group --this person might do a minimum of 2 hrs per month of work on this group

Contributor/Participant --this is a person who may be involved with building/maintaining one or more areas within the group --this person should be active and reactive in building/maintaining --this person is concerned --this person might do a minimum of 1 hr per month of work on this group

Affiliate --not sure what to call this role to connote a much less active role, solely an association with the group --this person is someone who wants the Group to appear in My Groups in his/her My Curriki, but doesn't necessary want to be involved in an active way --person wants to stay up-to-date on the group's activities --this person does not wish to be expected to contribute any time --this person might do a minimum of 15 mins per month of work on this group


Figure 11- Invite member to join group


THE MESSAGES (PLOG) TAB

The Messages Tab is the primary communication interface for group members. The messages tab is not available (Grayed-out) to visitors of closed group. It is available otherwise, however only members can create messages or comment on message even in an open group. Messages are addressed to recipients, which might be the whole group, just certain roles or certain members. As a result, visitors to open groups will only be able to see messages to the entire group. Members of groups can see message to them, their role or the entire group. Admins, however, can see all messages, even if from one member to one other member.

There may eventually be three different types of Plog entries, each with its own editing interface and display behaviors. Initially, only the first element, Messages, will be implemented.

For complete copy for the Groups Messages tab, please refer to [Group Messages Tab section of the Copy for Groups Document]

Messages- Effectively a Message is a discussion board where members can send notes to the entire group, to specific roles or individuals. A message is a wiki page, and can contain attachments, and include comments. Comments can be used as a form of discussion thread, but with only one level. (e.g. no comments on comments.) However, using the ability to send a message to individuals and roles, in addition to the entire group, messages can be used more like an e-mail system.


Figure 12- Messages Tab

MESSAGE TAB ELEMENTS:

1) About Messages area is a collapsible panel introducing and describing the uses of the message feature. It should be an editorially managed wiki page/panel that can be added or removed to the layout easily. It will have default text, and group admins can edit it (With an edit button in the title) to customize it for their group (Note, this should be a generalized style book element/macro It is used in several tabs)

2) The Create Button area is where users can create new messages. Visitor to open group do not get this element (Visitor to closed groups can't see this tab). This will be extended to include Create Event, and Create Task in future releases.

3) The Messages area is where message are displayed. It has three sub parts:

a. The Filter Selector area is where users can select what messages are displayed in the list area below. The default is "To Group" which means messages directed to the entire group. Members, but not visitors, also see "To Me", meaning a message that is directed specifically to that member, and "To my role" meaning a message directed to the role the user selected in their group profile. Lastly, group admins see one additional filter that others don't have, and that is "To All" meaning every message in the group, even from one individual to another (Point-to-point).

The Filter area will be extended in future releases to include search and sort capabilities.

b. The Message List area is where the messages are displayed. It functions similarly to the "Polg" in the Chronopolys system. All group messages that match the selected filter are listed chronologically, up to 20 per page. Each message article has two modes, collapsed and expanded, and messages are initially listed in their collapsed form. Clicking on the "Show" button expands the full body of the message, and “Hide” to collapse the message body. (See the wireframe and the Chonopolys plog for reference.) The head has the time and date stamp (With month spelled out) and the creator of the message (Who's name links to their My Curriki page). Next is the title of the message. When expanded, you see the body of the message. In the footer of the message are some links. "Read this message" takes the user to a page with the article and all its comments listed below it the Read Message Page (Below). Edit, available only to group members, takes the user to the Edit Message page (See below.) (#) Attached files takes the user to the Attached File List section of the view message page. Lastly (#) Comments lists how many comments there are, and if there are any, links to the comments section of the view message page.

c. The Paging Area- This functions identically to the paging mechanism for search. When paging, you maintain your state in the tabs.

(Future Feature) Events – This is like a meeting request. It includes a time and location It can be directed to the entire group, a specific role, or individual group members(s). The interface allows invited members to indicate they plans to attend or not.


(Future Feature) Tasks- Tasks are central to group project management. Tasks can be assigned to the whole group, specific roles or to individuals. A task has one of three states, Pending, Active and Completed. When a user accepts a task and/or updates its percentage complete, it is considered active (For that user). When it is marked as 100% complete, it is treated as a completed task. Another important element of tasks is that they can be associated with specific resources in the group collection, and if they are, will appear in the CB when that asset is displayed. (See description of the Task tab in the CB below.)

NOTIFICATIONS BY E-MAIL IN MESSAGING:

Users, when creating or editing a Message entry, have the option to send an e-mail notification of the new entry or edited entry to all users to whom the entry is addressed. When a notification is sent, the link to the view message page and the actually formatted HTML content of the message is included in the e-mail. (Note: This may need a little designing) However, each group member, in their group profile, can choose to opt-out of e-mail notifications for the group. In either case, users can see their Message Entries in their My Groups area of their My Curriki page (see update My Curriki wireframes), or my using the Message tab (plog) view filters (To Group, To Me or To My Role) – See create Edit message below.

Notification messages that are sent from the system are addressed from [email protected] . The message should include direction on how to not receive further nonfictions from the group (Edit your group profile, ore remove yourself from the group) in the small print on the bottom of the message. The title of the e-mail is “Group Name Message notification: message name” and at the top is should say “No not reply to this e-mail” and the include the link to the view message page for this message. In the middle of the e-mail message, in a box, is the formatted HTML of the message (Again the real copy can be found in the Copy for Groups document) .

VIEWING (READING) A MESSAGE

When a user clicks to view a message, the view the message view page. This page is intended to enable on going dialog and commentary on a topic.

mailto:[email protected]


Figure 13- View Message

In the view message page, delete and edit is only available to the person who created a message or comment, and group admins. Members can not delete or edit other member’s messages, nor can they delete another member’s comment. If a message is deleted, all comments associated with it are


deleted. (Note: The creator of a message might be able to delete a comment to their message made by another member.) If delete is selected, a Java Script warning appears with a yes/no confirmation.

(Please note: It would be very good if there is a way to retrofit to resource and blog comments a delete button so someone who made a comment can remove it.)

In this View Message page, members of the group can add comments and attachments. Just like the Current Resources and Blog comments, clicking on the add comment button, opens a simple text entry box comment DIV area in the current page, with a submit button. Similarly, the browse and upload button for attachments function the current page.

Figure 14- Add comment or file to message


CREATE EDIT MESSAGE

If a group member has chosen to create a message, they are shown the edit message page:

Figure 15- Create/Edit message


For copy for this page please see [Create Edit Message in the Copy for Groups Document]

The elements of this page are:

1) The Breadcrumb & Group Title Banner - This is showing the fact that we are now in a sub-page of the messages tab. You can go back to the main message page by clicking on the breadcrumb, or by clicking on the message tab itself. Any click that would lose entered info should give a JS warning.

2) The Tabs - Same functionality as the rest of the groups’ area

3) The About Creating Message panel – This is an editorial managed help panel and should be easy to modify and removed from the layouts. Only Group admins and system admin can edit. Anyone can hide/show. Default is show. (Store status in user cookie if you can)

4) The Edit Message area – contains

a. The Edit Title area- The title of the message

b. The Edit Message area - (Uses the WYSIWYG editor) with the option to switch to source edit more. This includes all the functions of the WYSIWYG editor, including add image or file or link, etc.

c. The “Send To” area - The default is to the entire group. However, you can also select to send it to one or more roles and/or one or more individual group members. If the “To” Roles or the Members check box is selected, the associated drop box becomes active. In the drop box is the list of role/members. You can select a roll or member and click “Add” next to the drop box. This adds that person or role to the ‘To’ list. The drop box moves down one line and the list removes the one item just added so you can now select another role or member to add. You can continue until all roles and members your want to include are listed. If you added one role or person that you would like to not include, there is “Remove” link next to the name of each added remember or role. If an individual is also in a role (And obviously in the whole group) they only get the message once, but can find it in message under the appropriate filters. Please note, that the person who creates a message is treated as one of the recipients, so it is always in their My Message and in the Messages Tab with the “To me” filter.

d. The Send Notification option – This is defaulted off. This is used by the creator/editor to send an e-mail copy of the message and notification to all members in the Too list (If listed specific, if part of an included role, or if to the entire group.)


Figure 16- Interface for adding to the "To list" of a message

If user selects Cancel, clicks on a Tab, on the breadcrumb or on the left nav (Anything that would take them out o the edit message page without sending, a confirmation JS is presented (“Your message has not been sent, are you sure you want to cancel.? Yes/No”), If the Save/Send button is selected, a check is done to make sure at that there is someone in the ‘to’ list, and if not an error is presented (Please selected a “Send to” option). If there is at least one recipient, the user is returned to the message tab in both cases, and the new message is at the top of the list. The system send any notifications, and posts the message.

THE CURRICULUM TAB

The curriculum tab is like a user’s “My Collections” in that it is where a group keeps is shared collections, but also where they can access the group contributions.


Figure 17- Group Curriculum Tab


ELEMENTS OF THE GROUP CURRICULUM TAB:

For copy on this and related pages, please see the [Group Curriculum Tab of the Copy for Groups Document]

1) Breadcrumb & Group Title Banner – The breadcrumb here is Group Name > Curriculum

2) About Creating Group Resources and Collections is a collapsible panel and editable wiki block introducing the group collections tab and how to use the group collections and organization. It has default language, but a Group admin(s) can edit this, in the general Wiki editor interface, to contain whoever they like. This includes changing its header bar title by changing the title of the page. Members and visitors do not see the edit button. When this is edited, it is edited under the Curriculum tab in a sub-page “Edit About Creating Group Resources and Collection.” Refer to the Edit Wiki section for the Documents Tab for the details as this functions identically under this tab and identically to Edit Welcome Message on the Home page tab.

3) Search Group Contributions – This is exactly the same as the search group resources on the group home tab. When the user enters a search term (Or selects search without a term to see all contributions listed), displays the advanced search interface, but under the group Curriculum tab, and it pre-filters to only assets in group collections space. In this box also is the “View All” button that displays the new “Group Contributions table” under the “Curriculum” tab. (Note this same table, is used in the new My Curriki under the My Contributions Tab.)

4) The Group Collection area – This lists all of the group Collections. If there are more then 10 (A system configurable value), then the standard paging mechanism is added to the bottom of the box area.

a. The Hide Description button – In the header for the area, collapses the descriptions for the collections below, showing just the collection title bars (ICT icon, title and function buttons). If hidden, the button becomes “Show Descriptions.”

b. Add New Collection Button - This launches the add path for creating a collection. Any member can create a collection (Though group admins may want to turn this off and only let certain rolls create collections.) [Jennifer to check the copy in the add path case.]

c. A Collection (One of N)– Contains the collection title bar, functions and description (If not hidden).

i. View – Available for any group member and visitors if rights allow (Protected or Open). If the rights are set to Private, then that collection does not appear for visitors.

ii. Edit – This is available to all Members, and logged-in visitors if the rights are open.

iii. Add (Asset) – This is also available to all group members, and also logged-in visitors if the rights are open. This button starts the same add path as ‘add to collection” in My Collections, but the asset is being added to the appropriate group collection in the group collection space, and will be treated as a group


asset. The dialog that pops-up when this is selected is “Add a resource from Curriki’s Repository”, “A file from your computer or a Web Link” and “A new file to be created using a Curriki Template”.

iv. Delete – Delete collection is only available to group admins. (This may be removed in favor of the delete in the contributions table.) If selected, there is a confirmation dialog “This can not be undone. Are you sure you want to delete?”

v. Paging Footer for list – Same as search

THE GROUP VIEW ALL CONTRIBUTIONS SUB-PAGE OF THE GROUP CURRICULUM PAGE

If the user selected View All Contribution form the Curriculum tab, they see the full list of all group resources.

Figure 18- Group Contributions Table


ELEMENTS OF THE GROUP CONTRIBUTIONS TABLE:

1) Contributions Label – Indicates that you are in a sub page of the Curriculum Tab. You can go back to the Curriculum tab by using the breadcrumb or the Tab itself.

2) The Table- The table is storable (Except Action). The table Columns are

a. Title- When you roll over a title, a Div Box (Like Search) appears with the description and metadata. Titles wrap and then are truncated is to long. Clicking on a title takes you to the view page for that resource

b. ICT- This column shows just the ICT icon without a label. If you roll over an icon, the tool tip shows the label.

c. Last Updates – This is the default sorting field (And as such should have the underline illustrating this fact.)

d. Access – Lists the access privilege setting for this asset

e. File Type - Lists the file type icon, again without a label. If you roll over the icon, the label is displayed as a tool tip

f. Action – What is in the Action column dispends on the asset and the user who is viewing. Only the group admin and the original contributor see the Delete option. Edit is available if rights allow. If delete is selected, there is a JS confirmation dialog box warning “This can not be undone. Are you sure you want to delete?”.

3) Standard Paging Footer – Same as Search, pages though the results.

When you roll over a title, a DIV box pop-up containing the Description (The first 5 lines, and if a line is too long without a space or wrapping point, then it is truncated.), Subjects (2) and educational levels (2) is displayed. The upper left corner of the box is positioned where the courser is pointing when over a title. Also tool tips for the two icons in the table present the File Type and ICT type name.


Figure 19- Pop-up info dialog in group contributions

THE SEARCH GROUP RESOURCES SUB-PAGE OF THE GROUP CURRICULUM PAGE

If the user enters a query and uses the search button from the Group Home or the Group Curriculum tab, the search group resources page is displayed. This is the standard Search GWT element, but only searching against resources in the group collections. The interface is identical otherwise, except it is placed under the Group’s “Curriculum” tab. Like other sub-pages of tabs, you can return using the breadcrumb or the tab itself.


Figure 20- Search Group Resources

THE MEMBERS TAB

The Members Tab is where group members can see the other members of the group, their roles, link to those members “My Curriki” page, and where they can edit their own group profile. It is also where group administrators for closed group approve or reject membership requests and nominations. Editing your own group profile includes opt-out or opt-in for notifications for the group, and the ability to remove yourself from the group. Group Administrators can edit any group member’s profile, including the ability to remove members. When a user sees an edit icon in the member’s title bar, then they can edit that user’s profile. Visitors never see edit, group members can only edit their own profile, and admins can edit any members profile, but another admins.


Figure 21- Group Members Page (Admin view)

ELEMENTS OF THE GROUP MEMBERS TAB:

This tab is not available to visitors in closed groups. For exact copy for the Members Tab elements, please refer to the [Group Members Tab section of the Copy for Groups Document].

1) The About Group Membership Block – Like many of the other groups tabs, this first element is a wiki block. It has default text in it (See Copy document), but the group admin can edit this wiki block as well. It is edited in the same Wiki editor under the Members tab, just like the home welcome tab message is in its tab.

2) The Membership block (Invite or Join) – This works identically to the same box on the home tab. (Home page element 6, Membership Info box)- (See Copy for Groups Document for exact copy). Note unlike the home page, request membership does not appear here because this only occurs in closed groups, and visitors to closed group can not use the members tab.

3) The Manage Membership Requests area – This only displays in closed groups, and then only for group admins. For each invited user or Curriki member so completed the Membership Request from, there is an entry in this box (Listed oldest on the top to freshest on the bottm. It displays the applicant’s display name, and the group profile info they added to the request from. Their name links to that applicant’s My Curriki page. There are two buttons-

a. Accept – Adds the application to the group members list send the applicant a welcome to the group e-mail [See Copy for Groups Document]. The next time that user visits their My Curriki page, they will see the group in the “My Groups” tab.

b. Deny – The group admin uses this to reject the applicant. It brings up a e-mail rejection form where the admin must enter a reason or simple state that request has been denied. (This is based on the Send to a friend From. Needs copy and treatment.) This is sent to the applicant as an e-mail message from the group (same as for notifications).

4) The Group Members List – This displays for all members, and also for visitors to an open group. This is an alphabetical list of member cards. Each card has the member’s avatar image, their display name, and what role they have in the group. If there are more then 20 members (A system configurable number), then the standard paging metonyms is added. A future enhancement to this list is to add filters and sorting options, like sort my role, or sort by order of membership, or search members.

a. Edit Group Setting button – This button never displays for visitors. (And visitors can not access this tab if it is a closed group). The button displays for a group member only on their card, and no other card. Group admins can edit any member’s card, and their own, but can not edit the profile of another group admin.

b. Editing your profile – When editing your profile, you can select a new role or roles (But you can not select Group admin for yourself), or change your notification setting (Opt-out of group notifications, and request notifications of changes to your assets, messages and document. You can also remove yourself fro the group. If you select “remove from group” a JS confirmation dialog “Are you sure?” message is presented. If you select yes, then you are moved from the group and return to the group home page. Saving saves, can cancel cancels.


c. Editing someone else’s profile – A group admin can edit other group member’s group profile (But not other Group Admins). When they do they can choose a role or roles for them (Including giving them admin role and privileges), or remove them from the group. They can also edit the user’s group profile (But should not). The admin can not change the user’s notification options. However, the admin can choose to kick the member out of the group by choosing “Remove from Group”. In this case, a combination confirmation dialog and “Group dismissal” e-mail form is presented (Need copy and treatment.) The dialog box says, “Please explain to this member why you removing them from the group. To complete removing (user name) from group, complete your message and click ‘send notice and remove member’. To leave the member in the group and cancel the operation, click the ‘cancel’ button.” If the admin enters some text and chooses to remove the member, that member is removed form the group members list. The e-mail notification is sent to the rejected user from the group notification e-mail address.

THE DOCUMENTATION TAB-

The Documentation tab is a basic wiki and file storage area for the group intended to contain all group documents which are related to the group organization and activities but which are not learning resources. The tab is available to all group members, but also visitors to the visitors if an open group. The tab is not available too visitors to a closed group. Regardless, visitors can not create or edit Wiki pages, or upload documents. In an open group visitors can only view wiki pages and download documents in this tab.

The functions on this tab represented a simple Wiki page and attached file list. It is much like the documents and wiki implementation in Chronopolys. This tab leverages the base XWiki functionality with a different style sheet.

For all specific and full copy for this tab and its sub elements, please see the [Group Documentation Tab section of the Copy for Groups Document].


Figure 22- Group Documents Tab


ELEMENTS OF THE GROUP DOCUMENTS TAB

1) The About Creating Documents Area - Like the other tabs, this first element is a editorial Wiki block with default copy that can be edited and customized by the group admin(s). It is edited just like any other wiki page under this tab.

2) Add a wiki page – This element only displays if you are a group member. To add a wiki page, enter its title can click add, You are then taken to the generic Edit wiki page sub-page (See below)

3) Add a Document – This is also only available to group members. Browse bring up the browsers find file dialog, when you select and enter a file, the Upload button is available. After the upload the page is refreshed and the new file is added to the list area.

4) The group wiki pages and document list – This lists all group wiki pages and documents in the order created. 20 items appear on the first page (A system configurable value), and if there are more, the standards paging footer is added to the element. Clicking on the title or icon of a wiki page brings up the view wiki page sub-page. Clicking on the title of a document downloads that document. There is a Delete button, but that is only available to the group admins or the person who created the page or document. To edit an existing wiki page, first view it by clicking on its name.

Figure 23- View wiki page (Wireframe)

From View Wiki page, you can edit the wiki page if you are a group member, or delete it if you are the creator or a group admin.


Figure 24- Edit Wiki Page

When editing a wiki page, you have the full WYSIWYG editor. (You should also be able to switch to pure wiki mode.) You can also go to the History mode, but you are warned that any changes will be lost when you do switch from Edit WYSIWYG to History. Form the history mode View version, Compare versions and Rollback all display in the wiki page view display above. Save saves, and Cancel cancels after a confirmation, and both return you to the Document tab (Updated or not). The same interface is used to edit the Home page welcome message and the other Groups tab direction elements.

THE NEW MY CURRIKI

The new my Curriki page takes the current My Curriki elements and turns them into tabs. Two new tabs, “Favorites” and “My Groups” are added. The new tabs are order is:

1) Profile – (Displays different for the member viewing self vs. some other member)

The user profile is basically unchanged, it has just been placed under a visual tab. Adding or replacing an image works as it does now and is only available to the user who area this is. Editing the profile also happens under this tab as a sub-page (Indicated by adding “> Edit profile” to the breadcrumb). The user profile displays for all visitors, but never shows the user’s e-mail to anyone but them and system admins). (Might consider removing the question about hiding the profile).


Figure 25- My Curriki Profile Tab

2) Favorites – A new name for the user’s Default Collection

This is really the user’s Default collection, now called globally “favorites.” It is presented in its own tab as a list of resources (Not as a collection.). It is set to not appear in search and to be private to the owner. The tab presents a non-storable table with all the assets of the default collection (Favorites) listed in sequence (Not presented). The elements of the table are Title, Contributor, ICT, File Type and Action. The action Colum is only available the user who favorites these are, and the only action is to remove (From the Favorites collection.)

There is a button to “View all” which takes the user to a view composite asset page where this list of favorites is displayed as a collection. From there the owner can edit it as a collection or re-order it if they like. Clicking on a title takes the user to the view of that resource. Clicking on Contributor takes the user to that member’s My Curriki area. Profile tab. Hovering over ICT or file type icons display a tool tip with the type name. Clicking remove puts up a JS warning dialog asking if the user is sure. Yes removes and refreshed the page. Cancel, Cancels. There are 20 items listed on a page (A system configurable number), and there is the standard paging footer.

A decision needs to be made a out what to do with existing user’s default collections. Do we create a new Favorites collection, or turn any existing default collection into a favorites collection?


Figure 26- My Favorites

3) My Contributions – Like View All Resources in a Group

This is the new table for listing all the users contributions to their collections or anyone else’s (Or any groups as well.). The functionality is the same as with group in that the columns sort and there is a roll over on the title to show the info Div pop-up. Action is only available to the owner (And admins). 20 items display on a page (A system configurable number) and there is the standard apging footer for the table.


Figure 27- My Contributions table


Figure 28- My Contributions with Info pop-up

4) My Collections – The redesigned collection interface under the My Collections tab (Need revised treatment- Missing “Add button” as well)


Figure 29- My Collections

5) My Bolg – The full bog list page in a tab.

All sub pages from current implementation occur under the Blog tab as sub-pages- Create/Edit entry, comments. Only the owner can edit or delete a post. Members can comment, and delete their own comments (This is a change as users can not current delete their comments).


Figure 30- My Blogs

6) My Groups – A list of all the groups a member belongs to. Under each is a list of message to the user from that group (Still being designed.) If the messages section is included, visitors view another user’s My Curriki will see the groups but not the messages.


Figure 31- My Groups (Owners view) (Remove descriptions for owners view?)


Visitors to this member’s MyCurriki area do not see the user’s messages. They only see the groups the member belongs to with the group mastheads with descriptions.

Figure 32- My Groups (Visitors view)