Auronet 4 - Specification Document: Difference between revisions

From Auroville Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
This is a technical document meant for software developers. Edit it only if you know clearly what you are doing.  
This is a technical document meant for software developers. Edit it only if you know clearly what you are doing.  


If you have general ideas please post it in '''[[AVnet 4|AVnet 4]]&nbsp;&nbsp; &nbsp;&nbsp;'''<br> Click through mock up is available here: http://www.bardo.in/avnet/
If you have general ideas please post it in '''[[AVnet 4|AVnet 4]]&nbsp;&nbsp; &nbsp;&nbsp;'''<br> Click through mock up is available here:  


#The mock up code should not be used for building theme for the site, theme should be tableless CSS based cross browser compatible code.
http://www.bardo.in/avnet/


Auronet portal will be based on Drupal Open Source CMS  
#The mock up code should not be used for building theme for the site, theme should be tableless CSS based cross browser compatible
 
code.
 
Auronet portal will be based on Drupal Open Source CMS


#To make sure migration to future versions of Drupal, the Drupal core shall not be modified
#To make sure migration to future versions of Drupal, the Drupal core shall not be modified
Line 12: Line 16:


#Only people are allowed to register as a user.  
#Only people are allowed to register as a user.  
#Working Groups, Services, Communities etc are created as Groups (Refer Groups)  
#Working Groups, Services, Communities etc are created as Groups (Refer Groups)
#Every user will be belonging to one or more groups.  
#Every user will be belonging to one or more groups.  
#A user can register as a member of the site only by invitation  
#A user can register as a member of the site only by invitation  
#All RA Members can invite new people ( RA member or Non RA member ) to become a user.The invitation form should specify that only people not working groups or units etc can be invited to be a member and while
#All RA Members can invite new people ( RA member or Non RA member ) to become a user.The invitation form should specify that only  


sending invitation, the role of the member should be specified. ie. whether RA member or not. Invitation also should specify to which group a user is invited.
people not working groups or units etc can be invited to be a member and while sending invitation, the role of the member should be  


specified. ie. whether RA member or not. Invitation also should specify to which group a user is invited.
#Membership requires approval from the Site Administrator  
#Membership requires approval from the Site Administrator  
#All Non RA members requires a RA member as an invitee  
#All Non RA members requires a RA member as an invitee  
Line 29: Line 34:
#RA Member  
#RA Member  
##Can create group  
##Can create group  
##Can invite new people to Auronet who will be permitted within the groups where they have been invited if the groups is open to invitation.<br>  
##Can invite new people to Auronet who will be permitted within the groups where they have been invited if the groups is open to  
 
invitation.<br>  
##Can view, create, edit, delete content types available within groups depending on permissions within each group.  
##Can view, create, edit, delete content types available within groups depending on permissions within each group.  
#Un authenticated user - can see only the login page
#Un authenticated user - can see only the login page
Line 37: Line 44:
There will not be Roles within a group, instead Drupal's OG defaults will be used, ie. Groups Manager and Administrator.  
There will not be Roles within a group, instead Drupal's OG defaults will be used, ie. Groups Manager and Administrator.  


OG Subgroup functionality may be used in the future if a group needs subgroups. However this feature need not be implemented in this version. Function reserved for the future.  
OG Subgroup functionality may be used in the future if a group needs subgroups. However this feature need not be implemented in this  
 
version. Function reserved for the future.  


== Groups  ==
== Groups  ==


Based on Drupal OG  
Based on Drupal OG


#All users in the role RA Members can create groups.  
#All users in the role RA Members can create groups.  
#Each group can have unique visual identity given by a header image and a right column carried by all documents posted in that group.  
#Each group can have unique visual identity given by a header image and a right column carried by all documents posted in that group.  
#Each group will have its unique categories to classify its nodes, this will be defined by the Group Administrator  
#Each group will have its unique categories to classify its nodes, this will be defined by the Group Administrator  
#Groups be classified, example: Working Groups, Communities, Services, Farms, Schools etc<br>
#Groups are classified into cateogries (taxonomy), a group can belong to multiple categories
##Working Groups
##Services
##Schools & Educational Centres
##Art & Culture
##Planning & Architecture
##Health # Healing
##Farms
##Communities
##Economy & Business
##Design & Crafts
##Food & Recreation
##Study Groups
##Special Interest Groups
#There can be multiple Group Administratotors  
#There can be multiple Group Administratotors  
#Minimum of one Group Admin should be a Residents Assembly member<br>
#Minimum of one Group Administrator should be an RA member


=== Membership  ===
=== Membership  ===
Line 58: Line 80:
#Follow OG default sharing - audiance, subscription options for content types available within a group.  
#Follow OG default sharing - audiance, subscription options for content types available within a group.  
#Article content type will have additional wiki option - see Arcticle content type details.  
#Article content type will have additional wiki option - see Arcticle content type details.  
#OG default 'Public' option will not be available for all the groups. This option is reserved exclussively for Site Managers, to send selected nodes to public site www.auroville.org  
#OG default 'Public' option will not be available for all the groups. This option is reserved exclussively for Site Administrator, to send selected  
#Emailing a node - send link to a node or the entire content of the node to one or more email id's<br>
 
nodes to public site www.auroville.org  
#Emailing a node - send link to a node or the entire content of the node to one or more email id's


=== About us  ===
=== About us  ===


This will be a static content block in the right column, an editable html area where Group Administrator can post links. Edit link will be available only to the Administrator.  
This will be a static content block in the right column, an editable html area where Group Administrator can post links. Edit link will be  
 
available only to the Administrator.  


=== Categories  ===
=== Categories  ===
Line 75: Line 101:
##Articles and  
##Articles and  
##Surveys  
##Surveys  
#By default, the following categories will be available to all groups. These categories may be renamed, removed or reordered by the Group Administrator or Site Administrator according to the needs of a specific group.  
#By default, the following categories will be available to all groups. These categories may be renamed, removed or reordered by the Group  
 
Administrator or Site Administrator according to the needs of a specific group.
##Events  
##Events  
##Announcements  
##Announcements  
Line 81: Line 109:
##Discussions  
##Discussions  
##Surveys  
##Surveys  
##Files  
##Files
#Each category will indicate the number of nodes in that category.
#Each category will indicate the number of nodes in that category.


Line 92: Line 120:
##Title  
##Title  
##Location  
##Location  
##Event type - predefined taxonomy terms common to all groups. Eg. Cinema, Dance, Theatre, Talk, Exhibition, Presentation, Workshop, Seminar, Class, Course  
##Event type - predefined taxonomy terms common to all groups. Eg. Cinema, Dance, Theatre, Talk, Exhibition, Presentation, Workshop,  
 
Seminar, Class, Course
##Time  
##Time  
##Image - image will have a fixed position, max width 500 pix.  
##Image - image will have a fixed position, max width 500 pix.
##Description  
##Description  
##Author  
##Author
##Category - predefined taxonomy terms specific to each group in which an event is posted. Refer Group Category.  
##Category - predefined taxonomy terms specific to each group in which an event is posted. Refer Group Category.
#Events are of 3 types  
#Events are of 3 types  
##Events that occur only on a given date and time; example: dance performance  
##Events that occur only on a given date and time; example: dance performance  
##Events that last many days: example: a seminar / exhibition  
##Events that last many days: example: a seminar / exhibition  
##Events that are repeating; example: a weekly study class, yearly festivals, monthly workshops  
##Events that are repeating; example: a weekly study class, yearly festivals, monthly workshops  
#There should be an option to print shedule of a week's events - this is for anyone to take a printout to put on notice boards. Description and Author information need not be captured in such print out.  
#There should be an option to print shedule of a week's events - this is for anyone to take a printout to put on notice boards. Description and  
 
Author information need not be captured in such print out.  
#In the login page there will be listed the 'Coming Events', this will be full node listing of coming events for 7 days.  
#In the login page there will be listed the 'Coming Events', this will be full node listing of coming events for 7 days.  
#In the home page 'Today's Events' will be listed as shown in the mock up model, with Week and Month option links  
#In the home page 'Today's Events' will be listed as shown in the mock up model, with Week and Month option links  
##when there are no events for the day say "No events today"  
##when there are no events for the day say "No events today"  
#Events module home page will have full node linting of events for the coming seven days, i.e. Default view is 'Week', on the right column will be month grid with dates, selecting a date should list events for that date in
#Events module home page will have full node linting of events for the coming seven days, i.e. Default view is 'Week', on the right column will  
 
the left side. Current date will be highlighted in the grid.


be month grid with dates, selecting a date should list events for that date in the left side. Current date will be highlighted in the grid.
#All the events that are over and more than 1 year old will be automatically deleted from the database.
#All the events that are over and more than 1 year old will be automatically deleted from the database.


=== Article  ===
=== Article  ===


#Article type will be available in all groups.  
#Article type will be available in all groups.
#Article fields:  
#Article fields:
##Category - predefined taxonomy terms specific to each group in which an event is posted. Refer Group Category.  
##Category - predefined taxonomy terms specific to each group in which an event is posted. Refer Group Category.  
##Title  
##Title
##Tags - user defined taxonomy  
##Tags - user defined taxonomy  
##Description  
##Description
##Attached Files - it should be possible to attach multiple files for download, showing file name, file size and description of files attached.  
##Attached Files - it should be possible to attach multiple files for download, showing file name, file size and description of files attached.
##Author  
##Tick box to accept 'Rules of the Game'
##Date  
##Author
#An article node can be made into a Wiki page (editable by those who have access to it) on per node basis. Ideally this has to be done without modifying OG core module, if not possible consider using an additional
##Date
#An article node can be made into a Wiki page (editable by those who have access to it) on per node basis. Ideally this has to be done  


content type dedicated to behave as wiki page as it is in the OG module defaults.
without modifying OG core module, if not possible consider using an additional content type dedicated to behave as wiki page as it is in the  


#Readers can comment on articles, comments will be threaded, threading format is shown in the mock up model  
OG module defaults.
#Readers can comment on articles, comments will be threaded, threading format is shown in the mock up model
##When reply button is clicked for an existing comment, the data entry field should open right there below the comment to which the reply is to be made.
##Article type will have Rivision feature to keep in record all changes happening to the document.  
##Article type will have Rivision feature to keep in record all changes happening to the document.  
##There should be a 'Diff' feature to locate the difference between two versions of a document.
##There should be a 'Diff' feature to locate the difference between two versions of a document.
#There should be access count showing homany uniqe users have accessed an Article node.


=== Issue  ===
=== Issue  ===


Purpose of this module is to enable any registered member of Auronet to report issues to a Group and follow it up through threaded discussion. Technically an issue is a node with comments but with a specific access  
Purpose of this module is to enable any registered member of Auronet to report issues to a Group and follow it up through threaded  
 
discussion. Technically an issue is a node with comments but with a specific access rights.


rights.
#Issue Tracker is a content type available for all Working Groups,  ( Working Groups are a set of groups with some specific features) for other


#Issue Tracker is a content type available for all Working Groups, ( Working Groups are a set of groups with some specific features) for other groups it is an optional.  
groups it is an optional.  
#All registered users can post issues to any group who has Issue Tracker  
#All registered users can post issues to any group who has Issue Tracker
#The issues posted by a user will be visible only to that user and the respective members of the group where it is posted.  
#The issues posted by a user will be visible only to that user and the respective members of the group where it is posted.
#Owner of an issue can view, edit, and delete an issue.  
#Owner of an issue can view, edit, and delete an issue.  
#Group members can view an issue and comment on it, they can edit or delete their comments.  
#Group members can view an issue and comment on it, they can edit or delete their comments.  
#There should be option for email alert between issue owner and the group members when an issue is posted or comments are made.  
#There should be option for email alert between issue owner and the group members when an issue is posted or comments are made.  
#Group members can opt out from email alerts from the issue tracker.  
#Group members can opt out from email alerts from the issue tracker.
#Issue can be closed by Group members who can post comments similar to Articles.  
#Issue can be closed by Group members who can post comments similar to Articles.
##A closed issue may be reopened by the author anytime.  
##A closed issue may be reopened by the author anytime.
##There will be archives of all the closed issues.  
##There will be archives of all the closed issues.
#Any visitor to a Working Group will be able to see how many issues are there unresolved and the total number of issues received in the last 30 days, but will not be able to see the issues themselves.  
#Any visitor to a Working Group will be able to see how many issues are there unresolved and the total number of issues received in the last  
#Issue fields:  
 
##Title  
30 days, but will not be able to see the issues themselves.
#Issue fields:
##Title
##Tags - user defined taxonomy  
##Tags - user defined taxonomy  
##Description  
##Description
##Attached Files - it should be possible to attach multiple files for download, showing file name, file size and description of files attached.  
##Attached Files - it should be possible to attach multiple files for download, showing file name, file size and description of files attached.
##Author  
##Author
##Date
##Date


=== Survey  ===
=== Survey  ===


Webform module of Drupal  
Webform module of Drupal


#Survey type will be available for all groups, with audience targetting.
#Survey type will be available for all groups, with audience targetting.
Line 164: Line 203:
=== Petitions  ===
=== Petitions  ===


Same as existing petitions module  
Same as existing petitions module


#Petitions will be availalbe only in the group 'Auroville Community', with OG audience targetting.  
#Petitions will be availalbe only in the group 'Auroville Community', with OG audience targetting.
#Any member of the group can initiate a petition, author can also delete the petition.  
#Any member of the group can initiate a petition, author can also delete the petition.
#Petition will be addressed to one of the groups of Auronet  
#Petition will be addressed to one of the groups of Auronet
#Fields are:  
#Fields are:
##Adressed to: Group selection list.  
##Adressed to: Group selection list.
##Title  
##Title
##Summary  
##Summary
##Description  
##Description
##End date  
##End date
##Post date  
##Post date
##Author  
##Author
#Petitions will have comments similar to Article comments  
#Petitions will have comments similar to Article comments
#A user may change signature option any time till the petition is closed.  
#A user may change signature option any time till the petition is closed.
#The group to which a petion is addressed will have an alert linking to the petition.  
#The group to which a petion is addressed will have an alert linking to the petition.
#A petition can be emailed with all its contents and signatures
#A petition can be emailed with all its contents and signatures


=== Directory  ===
=== Directory  ===


This is not a directory of Auronet registered users. It is a directory of Auroville telephone numbers and email ids maintained by the Telephone Department who will have the administrative rights to this content type.
This is not a directory of Auronet registered users. It is a directory of Auroville telephone numbers and email ids maintained by the Telephone  


#Directory fields  
Department who will have the administrative rights to this content type.
 
#Directory fields
##AV Name  
##AV Name  
##Community  
##Community  
##Phone  
##Phone  
##Fax  
##Fax  
##Cell  
##Cell
##Email  
##Email
##Masterlist Id  
##Masterlist Id
##Auronet user Id  
##Auronet user Id
#Auronet users list will be listed in a similar manner in the diectory page, data will be pulled from Auronet user's profile data set.  
#Auronet users list will be listed in a similar manner in the diectory page, data will be pulled from Auronet user's profile data set.
#An Auronet registered user can be mapped on to a directory entry, if there is a corresponding entry, and related data can be brought on to the user profile page.  
#An Auronet registered user can be mapped on to a directory entry, if there is a corresponding entry, and related data can be brought on to  
##If an Auronet user has profile mapped on the the directory, the user should be able to edit that data and submit for the approval of the Dirctory administrator. In that case the submitted data will over write the existing
 
the user profile page.
##If an Auronet user has profile mapped on the the directory, the user should be able to edit that data and submit for the approval of the  
 
Dirctory administrator. In that case the submitted data will over write the existing one only after the aproval by the Directory administrator.
#There should be option to export directory data as .csv file for importing into a spreadsheet; and this option should be available only the the


one only after the aproval by the Directory administrator.
administrator.
#In addition, the Directory listing page will have on the right side - refer mock up model - a set of static links, displaying tabular contents of


#There should be option to export directory data as .csv file for importing into a spreadsheet; and this option should be available only the the administrator.
some static pages containing tel. numbers useful organisations, places etc. They will be categories into different pages that can be
#In addition, the Directory listing page will have on the right side - refer mock up model - a set of static links, displaying tabular contents of some static pages containing tel. numbers useful organisations, places etc.


They will be categories into different pages that can be independently edited.  
independently edited.


=== Blog  ===
=== Blog  ===


#Every registered use will get a blog - this is where they publish everything that is their personal stuff.  
#Every registered use will get a blog - this is where they publish everything that is their personal stuff.
#Blog can have threaded comments similar to Article comments  
#Blog can have threaded comments similar to Article comments
##User can choose per node whether to allow comment or not.  
##User can choose per node whether to allow comment or not.
#Blog entry will be visible as per audience selected which depends on the groups a user is member of  
#Blog entry will be visible as per audience selected which depends on the groups a user is member of
#Blog fields:  
#Blog fields:
##Title  
##Title
##Tags - tags will be listed as categories on the right column with most repeated tages on the top, each tag showing the number of nodes in it.  
##Categories - Every user can have their own uniqe categories (taxonomy) to group their nodes. Categories will be listed as 'Categories' on  
 
the right column with most used ones on the top, each one showing the number of nodes in it.
##Description
##Description
#There should be access count showing homany uniqe users have accessed a blog entry


=== Bazaar  ===
=== Bazaar  ===
Line 221: Line 270:
Online market place where users exchange goods and services. See existing Bazaar in the AV net - Usability requires improvement.  
Online market place where users exchange goods and services. See existing Bazaar in the AV net - Usability requires improvement.  


#Bazaar fields:  
#Bazaar fields:
##Category  
##Category
##Title  
##Title  
##Description  
##Description  
##Image - image will have a fixed position, max width 500 pix.  
##Image - image will have a fixed position, max width 500 pix.
##Contact - name, email, phone  
##Contact - name, email, phone  
##Expiry date (default 1 month ahead, not for display, only to auto delete the posted item)  
##Expiry date (default 1 month ahead, not for display, only to auto delete the posted item)
##Date posting - author cannot edit this.  
##Date posting - author cannot edit this.
#Ads are grouped into categories - c  
#Ads are grouped into categories - c
#Site Administrator creates categories  
#Site Administrator creates categories
#Authors can edit their own content.
#Authors can edit their own content.


Line 242: Line 291:
#Quotes will be recycled only when there are no fresh quotes available in the database  
#Quotes will be recycled only when there are no fresh quotes available in the database  
#Least recycled and the oldest quotes will be reused in order  
#Least recycled and the oldest quotes will be reused in order  
#Quotes will be displayed in the home page  
#Quotes will be displayed in the home page
#Site Administrator add/edit/delete quotes
#Site Administrator add/edit/delete quotes


=== Downloads  ===
=== Downloads  ===
This module is to provide space for downloading software.
#Download fields:
#Category - predefined taxonomy terms
##Created by Site Administrator
#Title
#Description
#Files - multiple files can attached.
##Each file will have name, file size and description
#All registered usres can download any file
#There should be a download statistics
=== Pulse  ===
Functionality similar to Advanced Poll module of Drupal http://drupal.org/project/advpoll
#Pulse will be using this module to generate its questions.
#Pulse content type is available only within 'Auroville Community' and 'Residents Assembly', with OG audience targetting
#Pulse will have threaded comments option.
== Weather Module  ==
Weather module showing Pondicherry weather for the coming one week, shown in the home page.
== Image of the Day ==


Downloads module similar to what is existing in AVnet
Login page will have image of the day, displayed from a collection of images.
#Only width of the image is fixed, height is variable.
#Caption will be displayed over the image with a transparent background
#If necessary Site Administrator should be able to specify date for an image so that it comes on that date.


=== Pulse  ===


Functionality similar to Advanced Poll module of Drupal http://drupal.org/project/advpoll


#Pulse will be using this module to generate its questions.  
== About Auroville, References and Help  ==
#Pulse content type is available only within 'Auroville Community' and 'Residents Assembly'
These are three books - nodes heirarchically organised
#These pages will have wiki feature, ie, reader can also edit the content, also track versions and diff.
#All registered users can edit these pages.


== General details  ==
== General details  ==
Line 269: Line 343:
=== Home page  ===
=== Home page  ===


==== Toy grey band  ====
==== Top grey band  ====


Right side links, all open in a new window  
Right side links, all open in a new window  
Line 281: Line 355:
#TV - http://www.aurovilletv.org
#TV - http://www.aurovilletv.org


Logo band  
==== Logo band ====


#Logo - link http://www.auroville.org.in  
#Logo - link http://www.auroville.org.in  
#Home  
#Home  
#About Auroville - Goes to a book first page, hierarchic nodes, editable by members of the group 'Auroville Website'  
#About Auroville - Goes to a book first page, hierarchic nodes, editable by members of the group 'Auroville Website'  
#Groups - Goes to&nbsp;  
#Groups - Goes to;  
#'''Public tab left column '''  
#'''Public tab left column '''  
##Everything published in the groups and shared with the group Residents Assembl  
##Everything published in the groups and shared with the group Residents Assembl  
##Regardless of the individual who posted it, author name will not be shown in this column, only the name of the group will be shown as author
##Regardless of the individual who posted it, author name will not be shown in this column, only the name of the group will be shown as  
 
author
 
==== 5 Star rating ====
 
There should be 5star rating feature for the following content types.
#Article and related comments
#Blog and related comments
#Download
 
==== WYSIWYG HTML editor ====
 
The 'Description' fields of all content types and their related comment fields will have WYSIWYG HTML editor
Example:http://www.bardo.in/avnet/july27/Publish1.html#
The Editor will have the following options:
#Styles
#Bold
#Bulletted list
#Numbered list
#Link
#Image - to facilitage inserting image from the local machine, image should be automatically size optimized for the web, with maximum width
 
500px.
#Code View
 
==== Tool Tips ====
 
There should be dynamic contextual tool tips for all data entery forms to help the user, example is shown in the mock up model publishing
 
sequence. A tool tip need to appear only when the cursor moves over the input field and its related area.
 
 
==== New Members ====
 
This is a listing in the home page, latest 4 members who joined Auronet.
#shows only photo, it will be a link to their profile, if no photo is given dummy will be used.
#While hovering the photo the user name should be shown over the image.
#This is an automated dynamic listing.
 
==== Edit buttons ====
For the Site Administrator or Group Administrator to edit the contents 'Edit' buttons will be shown when they hover over the areas where they
 
have editing rights. Clicking on the button will open up a new layer on the top of the current page with light box effect.
The following will have hidden edit button that shows up only when hovering.
 
#Home page
##Quotes
##Highlights
#Groups
##Group header image
##Group description
##Group alert messages
##Group links ( About us )
##Group categories
#Blog
##Blog categories
#Directory
##entries
##right column links
 
For the general node Edit / Delete / Revision etc links, see http://www.bardo.in/avnet/july27/Article.html
This pattern can be used for all node types.
 
==== Publish buttons ====
In the home page 'Publish' button will be shown only while hovering over an area, this is applicable to the following.
 
#Public tab, both columns
#Events
#Pulse
#Survey
#Bazaar
#Downloads
#Petitions
 
In the respective home pages of these modules there will be static visible publish button.
 
==== Publishing Work Flow ====
#An article will have three statuses
##Draft stage - it is saved by the author to complete.
##Waiting for Approval - A completed article is submitted and is waiting for approval by the Group Administrator. Approval is required only if
 
an article is targetting audience outside the group where it is getting posted. Within a group approval is not required. A group may decide not
 
to have approval process at all, this should be possible on a per group basis.
##Reverted - Article has been reverted back to the author for modification - with an enclosed note from the Group Administrator.
##Rejected - Article has been rejected, with an enclosed note from the Group Administrator.
##Approved - The article goes visible to its target audience and an email alert goes to the author about approval.
 
==== Contact Forms ====
Every registered user can be contacted by a contact form, the email id in the profile can be a link opening cotact form
In the directory, email id's can made into links that open a contact form.
#all contact forms will have 'Send me a copy' option
 
==== Flagging Content ====
#Reders can flag an article, survey, petition or blog or their related comments if they find it inappropriate
##While flagging an article or comment they can specify why they flag it.
##Site Administrators and Group Administrators gets email alerts when someone flags an article or comment
##Site Administrators and Group Administrators should be able to see the list of users who flagged and their messages.
 
====Rules of the game====
A single static page having Rules of the game, editable by the Site Administrator only.
 
====Red titles in the home page====
All red titles will be links taking to respective module's main pages or listing pages.


[[Category:Information_Technology]]
[[Category:Information_Technology]]

Revision as of 18:28, 7 August 2009

This is a technical document meant for software developers. Edit it only if you know clearly what you are doing.

If you have general ideas please post it in AVnet 4     
Click through mock up is available here:

http://www.bardo.in/avnet/

  1. The mock up code should not be used for building theme for the site, theme should be tableless CSS based cross browser compatible

code.

Auronet portal will be based on Drupal Open Source CMS

  1. To make sure migration to future versions of Drupal, the Drupal core shall not be modified

Users

  1. Only people are allowed to register as a user.
  2. Working Groups, Services, Communities etc are created as Groups (Refer Groups)
  3. Every user will be belonging to one or more groups.
  4. A user can register as a member of the site only by invitation
  5. All RA Members can invite new people ( RA member or Non RA member ) to become a user.The invitation form should specify that only

people not working groups or units etc can be invited to be a member and while sending invitation, the role of the member should be

specified. ie. whether RA member or not. Invitation also should specify to which group a user is invited.

  1. Membership requires approval from the Site Administrator
  2. All Non RA members requires a RA member as an invitee
  3. It should be possible to see who has invited whom, in both invitee's profile as well as the profile of the invited.

Global Roles

  1. Site Developer - Can do everything.
  2. Site Administrator - view, create, edit, delete all content types, manage users.
  3. RA Member
    1. Can create group
    2. Can invite new people to Auronet who will be permitted within the groups where they have been invited if the groups is open to

invitation.

    1. Can view, create, edit, delete content types available within groups depending on permissions within each group.
  1. Un authenticated user - can see only the login page

Roles within Groups

There will not be Roles within a group, instead Drupal's OG defaults will be used, ie. Groups Manager and Administrator.

OG Subgroup functionality may be used in the future if a group needs subgroups. However this feature need not be implemented in this

version. Function reserved for the future.

Groups

Based on Drupal OG

  1. All users in the role RA Members can create groups.
  2. Each group can have unique visual identity given by a header image and a right column carried by all documents posted in that group.
  3. Each group will have its unique categories to classify its nodes, this will be defined by the Group Administrator
  4. Groups are classified into cateogries (taxonomy), a group can belong to multiple categories
    1. Working Groups
    2. Services
    3. Schools & Educational Centres
    4. Art & Culture
    5. Planning & Architecture
    6. Health # Healing
    7. Farms
    8. Communities
    9. Economy & Business
    10. Design & Crafts
    11. Food & Recreation
    12. Study Groups
    13. Special Interest Groups
  5. There can be multiple Group Administratotors
  6. Minimum of one Group Administrator should be an RA member

Membership

Follow OG default options.

Sharing

  1. Follow OG default sharing - audiance, subscription options for content types available within a group.
  2. Article content type will have additional wiki option - see Arcticle content type details.
  3. OG default 'Public' option will not be available for all the groups. This option is reserved exclussively for Site Administrator, to send selected

nodes to public site www.auroville.org

  1. Emailing a node - send link to a node or the entire content of the node to one or more email id's

About us

This will be a static content block in the right column, an editable html area where Group Administrator can post links. Edit link will be

available only to the Administrator.

Categories

  1. Each group can have its own unique categories (taxonomy) to list its nodes
  2. Group Admin can Add, edit or delete categories
  3. Group Admin can reorgansise nodes from one category to other.
  4. A node can belong to multiple categories
  5. The following content types will have categories to belong to.
    1. Events
    2. Articles and
    3. Surveys
  6. By default, the following categories will be available to all groups. These categories may be renamed, removed or reordered by the Group

Administrator or Site Administrator according to the needs of a specific group.

    1. Events
    2. Announcements
    3. Meeting Reports
    4. Discussions
    5. Surveys
    6. Files
  1. Each category will indicate the number of nodes in that category.

Content Types

Events

  1. Event calendar with day, week and month views
  2. Event fields:
    1. Title
    2. Location
    3. Event type - predefined taxonomy terms common to all groups. Eg. Cinema, Dance, Theatre, Talk, Exhibition, Presentation, Workshop,

Seminar, Class, Course

    1. Time
    2. Image - image will have a fixed position, max width 500 pix.
    3. Description
    4. Author
    5. Category - predefined taxonomy terms specific to each group in which an event is posted. Refer Group Category.
  1. Events are of 3 types
    1. Events that occur only on a given date and time; example: dance performance
    2. Events that last many days: example: a seminar / exhibition
    3. Events that are repeating; example: a weekly study class, yearly festivals, monthly workshops
  2. There should be an option to print shedule of a week's events - this is for anyone to take a printout to put on notice boards. Description and

Author information need not be captured in such print out.

  1. In the login page there will be listed the 'Coming Events', this will be full node listing of coming events for 7 days.
  2. In the home page 'Today's Events' will be listed as shown in the mock up model, with Week and Month option links
    1. when there are no events for the day say "No events today"
  3. Events module home page will have full node linting of events for the coming seven days, i.e. Default view is 'Week', on the right column will

be month grid with dates, selecting a date should list events for that date in the left side. Current date will be highlighted in the grid.

  1. All the events that are over and more than 1 year old will be automatically deleted from the database.

Article

  1. Article type will be available in all groups.
  2. Article fields:
    1. Category - predefined taxonomy terms specific to each group in which an event is posted. Refer Group Category.
    2. Title
    3. Tags - user defined taxonomy
    4. Description
    5. Attached Files - it should be possible to attach multiple files for download, showing file name, file size and description of files attached.
    6. Tick box to accept 'Rules of the Game'
    7. Author
    8. Date
  3. An article node can be made into a Wiki page (editable by those who have access to it) on per node basis. Ideally this has to be done

without modifying OG core module, if not possible consider using an additional content type dedicated to behave as wiki page as it is in the

OG module defaults.

  1. Readers can comment on articles, comments will be threaded, threading format is shown in the mock up model
    1. When reply button is clicked for an existing comment, the data entry field should open right there below the comment to which the reply is to be made.
    2. Article type will have Rivision feature to keep in record all changes happening to the document.
    3. There should be a 'Diff' feature to locate the difference between two versions of a document.
  2. There should be access count showing homany uniqe users have accessed an Article node.

Issue

Purpose of this module is to enable any registered member of Auronet to report issues to a Group and follow it up through threaded

discussion. Technically an issue is a node with comments but with a specific access rights.

  1. Issue Tracker is a content type available for all Working Groups, ( Working Groups are a set of groups with some specific features) for other

groups it is an optional.

  1. All registered users can post issues to any group who has Issue Tracker
  2. The issues posted by a user will be visible only to that user and the respective members of the group where it is posted.
  3. Owner of an issue can view, edit, and delete an issue.
  4. Group members can view an issue and comment on it, they can edit or delete their comments.
  5. There should be option for email alert between issue owner and the group members when an issue is posted or comments are made.
  6. Group members can opt out from email alerts from the issue tracker.
  7. Issue can be closed by Group members who can post comments similar to Articles.
    1. A closed issue may be reopened by the author anytime.
    2. There will be archives of all the closed issues.
  8. Any visitor to a Working Group will be able to see how many issues are there unresolved and the total number of issues received in the last

30 days, but will not be able to see the issues themselves.

  1. Issue fields:
    1. Title
    2. Tags - user defined taxonomy
    3. Description
    4. Attached Files - it should be possible to attach multiple files for download, showing file name, file size and description of files attached.
    5. Author
    6. Date

Survey

Webform module of Drupal

  1. Survey type will be available for all groups, with audience targetting.

Petitions

Same as existing petitions module

  1. Petitions will be availalbe only in the group 'Auroville Community', with OG audience targetting.
  2. Any member of the group can initiate a petition, author can also delete the petition.
  3. Petition will be addressed to one of the groups of Auronet
  4. Fields are:
    1. Adressed to: Group selection list.
    2. Title
    3. Summary
    4. Description
    5. End date
    6. Post date
    7. Author
  5. Petitions will have comments similar to Article comments
  6. A user may change signature option any time till the petition is closed.
  7. The group to which a petion is addressed will have an alert linking to the petition.
  8. A petition can be emailed with all its contents and signatures

Directory

This is not a directory of Auronet registered users. It is a directory of Auroville telephone numbers and email ids maintained by the Telephone

Department who will have the administrative rights to this content type.

  1. Directory fields
    1. AV Name
    2. Community
    3. Phone
    4. Fax
    5. Cell
    6. Email
    7. Masterlist Id
    8. Auronet user Id
  2. Auronet users list will be listed in a similar manner in the diectory page, data will be pulled from Auronet user's profile data set.
  3. An Auronet registered user can be mapped on to a directory entry, if there is a corresponding entry, and related data can be brought on to

the user profile page.

    1. If an Auronet user has profile mapped on the the directory, the user should be able to edit that data and submit for the approval of the

Dirctory administrator. In that case the submitted data will over write the existing one only after the aproval by the Directory administrator.

  1. There should be option to export directory data as .csv file for importing into a spreadsheet; and this option should be available only the the

administrator.

  1. In addition, the Directory listing page will have on the right side - refer mock up model - a set of static links, displaying tabular contents of

some static pages containing tel. numbers useful organisations, places etc. They will be categories into different pages that can be

independently edited.

Blog

  1. Every registered use will get a blog - this is where they publish everything that is their personal stuff.
  2. Blog can have threaded comments similar to Article comments
    1. User can choose per node whether to allow comment or not.
  3. Blog entry will be visible as per audience selected which depends on the groups a user is member of
  4. Blog fields:
    1. Title
    2. Categories - Every user can have their own uniqe categories (taxonomy) to group their nodes. Categories will be listed as 'Categories' on

the right column with most used ones on the top, each one showing the number of nodes in it.

    1. Description
  1. There should be access count showing homany uniqe users have accessed a blog entry

Bazaar

Online market place where users exchange goods and services. See existing Bazaar in the AV net - Usability requires improvement.

  1. Bazaar fields:
    1. Category
    2. Title
    3. Description
    4. Image - image will have a fixed position, max width 500 pix.
    5. Contact - name, email, phone
    6. Expiry date (default 1 month ahead, not for display, only to auto delete the posted item)
    7. Date posting - author cannot edit this.
  2. Ads are grouped into categories - c
  3. Site Administrator creates categories
  4. Authors can edit their own content.

Quotes

  1. A quote has author and the text
  2. Quotes change every day i.e. stay for 24 hours changing at 00.00 hrs
  3. There are two types of quotes
    1. Quote specified to be displayed on a given date
    2. Quotes that can be recycled
  4. Quotes will be recycled only when there are no fresh quotes available in the database
  5. Least recycled and the oldest quotes will be reused in order
  6. Quotes will be displayed in the home page
  7. Site Administrator add/edit/delete quotes

Downloads

This module is to provide space for downloading software.

  1. Download fields:
  2. Category - predefined taxonomy terms
    1. Created by Site Administrator
  3. Title
  4. Description
  5. Files - multiple files can attached.
    1. Each file will have name, file size and description
  6. All registered usres can download any file
  7. There should be a download statistics

Pulse

Functionality similar to Advanced Poll module of Drupal http://drupal.org/project/advpoll

  1. Pulse will be using this module to generate its questions.
  2. Pulse content type is available only within 'Auroville Community' and 'Residents Assembly', with OG audience targetting
  3. Pulse will have threaded comments option.

Weather Module

Weather module showing Pondicherry weather for the coming one week, shown in the home page.

Image of the Day

Login page will have image of the day, displayed from a collection of images.

  1. Only width of the image is fixed, height is variable.
  2. Caption will be displayed over the image with a transparent background
  3. If necessary Site Administrator should be able to specify date for an image so that it comes on that date.


About Auroville, References and Help

These are three books - nodes heirarchically organised

  1. These pages will have wiki feature, ie, reader can also edit the content, also track versions and diff.
  2. All registered users can edit these pages.

General details

Clean URLs

  1. A group's home page will be : www.auroville.org.in/name-of-the-group
  2. A group's node will be www.auroville.org.in/name-of-the-group/xyz  where xyz is the node id
  3. A blog: www.auroville.org.in/blog/username/xyz
  4. A bazaar entry: www.auroville.org.in/bazaar/xyz
  5. A petition: www.auroville.org.in/petitions/xyz
  6. A blog: www.auroville.org.in/blog/username/xyz

Home page

Top grey band

Right side links, all open in a new window

  1. Email - http://mail.auroville.org.in
  2. Wiki - http://wiki.auroville.org.in
  3. .ORG - http://www.auroville.org.in
  4. .COM - http://www.auroville.com
  5. FS - http://fs.auroville.org.in
  6. RADIO - http://www.aurovilleradio.org
  7. TV - http://www.aurovilletv.org

Logo band

  1. Logo - link http://www.auroville.org.in
  2. Home
  3. About Auroville - Goes to a book first page, hierarchic nodes, editable by members of the group 'Auroville Website'
  4. Groups - Goes to;
  5. Public tab left column
    1. Everything published in the groups and shared with the group Residents Assembl
    2. Regardless of the individual who posted it, author name will not be shown in this column, only the name of the group will be shown as

author

5 Star rating

There should be 5star rating feature for the following content types.

  1. Article and related comments
  2. Blog and related comments
  3. Download

WYSIWYG HTML editor

The 'Description' fields of all content types and their related comment fields will have WYSIWYG HTML editor Example:http://www.bardo.in/avnet/july27/Publish1.html# The Editor will have the following options:

  1. Styles
  2. Bold
  3. Bulletted list
  4. Numbered list
  5. Link
  6. Image - to facilitage inserting image from the local machine, image should be automatically size optimized for the web, with maximum width

500px.

  1. Code View

Tool Tips

There should be dynamic contextual tool tips for all data entery forms to help the user, example is shown in the mock up model publishing

sequence. A tool tip need to appear only when the cursor moves over the input field and its related area.


New Members

This is a listing in the home page, latest 4 members who joined Auronet.

  1. shows only photo, it will be a link to their profile, if no photo is given dummy will be used.
  2. While hovering the photo the user name should be shown over the image.
  3. This is an automated dynamic listing.

Edit buttons

For the Site Administrator or Group Administrator to edit the contents 'Edit' buttons will be shown when they hover over the areas where they

have editing rights. Clicking on the button will open up a new layer on the top of the current page with light box effect. The following will have hidden edit button that shows up only when hovering.

  1. Home page
    1. Quotes
    2. Highlights
  2. Groups
    1. Group header image
    2. Group description
    3. Group alert messages
    4. Group links ( About us )
    5. Group categories
  3. Blog
    1. Blog categories
  4. Directory
    1. entries
    2. right column links

For the general node Edit / Delete / Revision etc links, see http://www.bardo.in/avnet/july27/Article.html This pattern can be used for all node types.

Publish buttons

In the home page 'Publish' button will be shown only while hovering over an area, this is applicable to the following.

  1. Public tab, both columns
  2. Events
  3. Pulse
  4. Survey
  5. Bazaar
  6. Downloads
  7. Petitions

In the respective home pages of these modules there will be static visible publish button.

Publishing Work Flow

  1. An article will have three statuses
    1. Draft stage - it is saved by the author to complete.
    2. Waiting for Approval - A completed article is submitted and is waiting for approval by the Group Administrator. Approval is required only if

an article is targetting audience outside the group where it is getting posted. Within a group approval is not required. A group may decide not

to have approval process at all, this should be possible on a per group basis.

    1. Reverted - Article has been reverted back to the author for modification - with an enclosed note from the Group Administrator.
    2. Rejected - Article has been rejected, with an enclosed note from the Group Administrator.
    3. Approved - The article goes visible to its target audience and an email alert goes to the author about approval.

Contact Forms

Every registered user can be contacted by a contact form, the email id in the profile can be a link opening cotact form In the directory, email id's can made into links that open a contact form.

  1. all contact forms will have 'Send me a copy' option

Flagging Content

  1. Reders can flag an article, survey, petition or blog or their related comments if they find it inappropriate
    1. While flagging an article or comment they can specify why they flag it.
    2. Site Administrators and Group Administrators gets email alerts when someone flags an article or comment
    3. Site Administrators and Group Administrators should be able to see the list of users who flagged and their messages.

Rules of the game

A single static page having Rules of the game, editable by the Site Administrator only.

Red titles in the home page

All red titles will be links taking to respective module's main pages or listing pages.