1. July 2010 D2.1 Upgrading strategy Javier Soto Catalog Release 3. Communities

2. May 2010 Detailed description of R3. Communities

3. May 2010 1. Highlight a blog to a community Abstract: Add an existing post from the portal blog to your community blog Description: Right now a community facilitator has the ability to highlight news, events, publications, etc. to the community, but not the blogs. The task consists here in allowing to highlight the blogs to the communities. Sections affected: Communities Technical tasks: Add a block, with the list of communities, the logged user is a facilitator in Create the process that links the desired blog with the community Add a “highlighted blogs” block to the community datasheet

4. May 2010 4. Highlighting portal content by members Abstract: Community members can also highlight content from the portal in their community by sending it to the facilitator. Description: Right now, only facilitators can highlight contents in the communities. The community members will have the possibility to propose the contents to their communities but will be visible to anyone only after validation of any of the facilitators. Sections affected: Communities Technical tasks: Make a block with the communities list the user is member Make the proposed contents visible to the community facilitators Add an “accept/deny” button to make the content public

5. May 2010 5. Access rights to shared documents Abstract: Shared documents will be assigned access rights based on a list generated by the facilitator Description: Currently, the shared resources are visible for all the logged users in ePractice. This task involves an improvement in the assignation for right. A list of options will be presented to the community facilitator with the following choices: - Public (registered and anonymous users) - Visible only or registered users - Visible only for community members Sections affected: Communities Technical tasks: Create a new section inside the “community resource” template with the access rights options. Modify the community page template to display the resources in function of their selected access option.

6. May 2010 8. WYSIWYG Tools Abstract: WYSIWYG Tools will be added all description creation pages. Description: In order to make easier the edition of text, add rich editors to the text fields. Sections affected: Communities Technical tasks: Install a rich editor library Configure it to cover all the text areas in communities.

7. May 2010 9. Send invitation to join the community Abstract: Allow sending invitations to other ePractice users to join the community Description: A possible improvement can be the “send an invitation” facility: it could be very useful to have the possibility to invite in your community people already registered to ePractice. E.g., some ePractice people who could be interested in joining the eProcurement Forum, but it is impossible to reach them since their e-mail addresses are not public. The invitation service could ask not only for e-mails to send the invitation too, but also epractice IDs. Sections affected: Communities Technical tasks: Insert a button to “send invitations to join the community” in the community page Open a form with a multi-selection of ePractice users, and a custom text The system sends an email to each ePractice user.

8. May 2010 10. Message to community members Abstract: Improve the usability of the message to community members process Description: A little inconvenience in the use of the community facilitator tool for sending messages to members has been found: if you want to contact several experts, visualized in different pages of the member list, it is necessary to send separate e-mails. The problem is that if you move from one page of the list to the next ones, the system cannot keep track of members already selected. Sections affected: Communities Technical tasks: - Change the process of the message box to manage all the checked users and not only those ones in the active page.

9. May 2010 11. Most active communities Abstract: Epractice members activity is measured by kudos, but there is no equivalent for communities. Description: The default order should be the 'recent activity', a figure that could be calculated as a compound index of several performance values during the last three or four months: - number of new members - number of actions done by the members (posting to the blog, uploading resources, etc) - number of actions done by the facilitators (sending messages, inviting members, etc) - number of visits to the community - number of extra kudos won by the community members In order to make this figure stable, the figures of at least three months should be considered. Also, other 'total' values could be integrated in the formula (but taking maximum 10% of the total weight): total number of users, total number of documents in the community, … Sections affected: Communities Technical tasks: Create batch process overnight which computes the score for each community and stores the result in the community datasheet. Offer a new filter option to sort the communities by “activity”. This option will be visible only to facilitators.

10. May 2010 12. Filter functionalities Abstract: Have a search functionalities within the communities' blog, news, and library (apart from the filter "all content/content inserted/ automatically/ content inserted by users'). Description: There's no search functionalities within the communities' blog, news, and library (apart from the filter "all content/content inserted/ automatically/ content inserted by users'). It is essential to have within the communities search functionalities similar to those in the general databases of cases, blog, news, and library; in any case add the filters by: tag, country. And if possible by other filters foreseen for the general case database: sector, status, type of initiative. So at present it is not possible to e.g. search past blog posts by theme. Sections affected: Communities Technical tasks: Expose the same Filter fields as in the portal general sections

11. May 2010 13. Embed information Abstract: Possibility for users to embed information Description: Community users cannot embed any information, e.g. RSS feeds or hyperlinks (as it can be done with the simplest blog elsewhere) in the blog posts, the library items, etc. It should be possible for community users to embed information. Sections affected: Communities Technical tasks: Install or check the rick editor library (i.e. FCK editor) Configure for active options: embed flash, image, rss, etc.

12. May 2010 15. Share resource limit Abstract: To raise the limit for “share a resource” from 5 to 50 mb. Description: Actually the limit for shared resources is very limited. This size should be increased. Sections affected: Communities Technical tasks: Change the source code of the file that controls the maximum size of uploaded files to 50 MB.

13. May 2010 17. Send message restriction Abstract: To allow the facilitator to decide if a new community member can send messages. Description: To allow the facilitator to delete the time limit of 1 month and 150 kudos to make possible to the members of his community to send messages from the first day. I do understand that this limit has been created to avoid spamming problems but, if a facilitator say “It’s ok, I know this guy” I think that it should be enough. Sections affected: Communities Technical tasks: Add a field in the user profile with the list of communities the user is allowed to send messages without any restriction. Change the validation process to include the new option

14. May 2010 19. Highlighted item comments Abstract: Add comments to highlighted cases, docs or events of the community Description: Possibility to add comment when highlighting cases, docs or events from ePractice: Sometimes, I find a case very interesting for our community, because of a specific think, but you cannot guess it directly from the title, therefore, it would be useful if the facilitator could add a remark about why the case is highlighted in the community. Sections affected: Communities Technical tasks: Open a popup after selecting the communities where the item will be highlighted Store the remark written in the popup as a special comment Modify the template for the “Highlighted….” sections to add a link or icon which opens a popup showing the remark.