GlobalNET_v1_3.pdf

GlobalNET System Description v1.3

14 January 2014

Summary

The Regional International Outreach (RIO) - Partnership for Peace (PfP) Information Management System (PIMS) program is an Office of the Secretary of Defense (OSD) initiative to deploy a common information technology platform to improve international partner outreach and collaboration efforts in a federated environment. GlobalNET, the platform resulting from a multiyear research and development effort of the RIO-PIMS program, is designed to support member communities’ current and future needs. It is a federated environment – characterized by the capacity of U.S. DoD and other communities to directly share participants and content across websites. This environment fosters networks of partner influencers and enables better use of DoD resources through collaboration among the Regional Centers for Security Studies, PfP and international partners, and other DoD educational institutions as required.

GlobalNET is an internet based collaboration, outreach, exercise , and communication enabling capability for members of the Regional Centers for Security Studies (Africa Center for Strategic Studies, Asia-Pacific Center for Security Studies, Center for Hemispheric Defense Studies, George C. Marshall European Center for Security Studies, Near East South Asia Center for Strategic Studies), the Combatant Commands, the Defense Security Cooperation Agency (DSCA), Office of the Under Secretary of Defense (Policy), NATO’s Military Cooperation Division, the PfP Consortium of Defense Academies, PfP Partner countries, and other designated institutions. It provides DoD and international partner security practitioners a platform to share information, collaborate on projects, and improve administrative activities. It also provides the ability to form collaborative communities of interest around security issues. GlobalNET provides allies and partner countries the ability to collaborate in critical cooperative activities. The platform supports coalition initiatives through development of distributive collaboration tools to reinforce aspects of approved cooperative activities. This support is important to achieve the interoperability/integration outlined in the Guidance for the Employment of the Force.

This document describes the GlobalNET platform requirements in support of the above mentioned goals.

Change Log: See Appendix H

Table of Contents Business Requirements Functional requirements

1.0 Login and Registration

2.0 User Profile

3.0 Communications

4.0 Groups

5.0 Events

6.0 Survey

7.0 Content Management System (CMS)

8.0 Search

9.0 Personal Dashboard

10.0 Notifications

11.0 Integrated Help

12.0 Reporting

13.0 Metrics

14.0 Online Learning

15.0 Video Teleconference (VTC)

16.0 Low Bandwidth

17.0 Mobile

18.0 Associate List

19.0 Navigation

20.0 User

21.0 Interface

22.0 Partnership for Peace Consortium (PfPC) Connections Journal

23.0 Policy Requirements

Planned Functional Requirements

1.0 Login and Registration

2.0 User Profile

4.0 Groups

5.0 Events

6.0 Survey

7.0 CMS

8.0 Search

11.0 Integrated Help

12.0 Reporting

13.0 Metrics

Appendices Appendix A: Member Communities Appendix B: Roles Appendix C: Permissions Appendix D: Taxonomy Appendix E: Network Diagram Appendix F: Minimum End User Requirements Appendix G: Governance Appendix H: Change Log

Business Requirements B1 The site shall improve the ease of which a user accesses the system B2 The site shall improve the ease of navigation for the user by including user-friendly labels, consistent navigation scheme, and improve methods of finding information and completing tasks

B3 The site shall provide the user with the ability to get access to information and documentation easily and provide a usable method for adding, editing, or removing content

B4 The site shall provide ability for the users to easily collaborate with each other online (via discussion threads, closed groups, commenting IM, blog, etc.)

B5 The site shall allow the user to run analytics to assess organizational goals

B6 The site shall better provide multiple workflows to accommodate the differing needs of the organizations that comprise GlobalNET

B7 The site shall provide a branding mechanism to allow associated sites to be properly identified with GlobalNET

B8 The site shall provide for secure access and maintenance of content and communicate the this level of security to the site to end-users

B9 The site shall provide the flexibility for the user to customize settings (i.e., privacy, language)

Functional requirements

ID Description Business

Requirement

1.0 Login and Registration

1.1 The system shall require users to supply a valid login and password to access the system

B1

1.2 The system shall provide a login area for existing users B1

1.3 The system shall provide a method for new users to

register with the site. This function will be available to non-authenticated users on the public site.

B1

1.4 The system shall allow the user to create their own

username but default to first.last

B1

1.4.1 The system shall verify if the username is available in the system

B1

1.4.2 The system shall prompt the user if the username is

unavailable

B1

1.5 During registration or a password reset the system shall

prompt the user to enter a password twice (for confirmation)

B1 B2

1.6 The system shall provide access to the current password

requirements during the password creation process.

B1 B2

1.6.1 The system shall provide feedback if the entered password fails to conform to the password requirements

B1 B2

1.7 The system shall allow any user to designate their

preferred language during registration.

B1 B9

1.8 The following information shall be collected as a part of the registration process:

- Name: Family, Given, Middle Name

- Preferred communication method & contact information for that method

- Username & password

- Country of residence

- Nationality

- Representation

- Organization

- Why are you requesting access?

- Additional remarks

- Employer

1.8.1 The system shall denote the data elements that are

required to complete in order to successfully submit an account registration request, including:

- Name

- Username & password

- Country of residence

- Nationality

- Email Address

B1

1.8.2 The system shall provide a predefined set of countries for the user to select their Country of Residence as part of the registration process

B1

1.9 The system shall communicate data entry errors and

provide guidance to successfully complete the registration process.

B1

1.10 The system shall notify a site administrator when an

account registration request has been submitted.

B1

1.11 The system shall notify the user of an approved or denied registration request

B1

1.12 The system shall communicate approved username (user-

defined) and a secure link to a one-time site login to the user upon approval.

B1

1.13 The system shall prompt the user to accept the Terms of

Use agreement registering for an account. The system shall store the fact that the user has accepted the Terms of Use and store a date and time associated with that.

B1

1.14 The system shall provide an option to contact a Site

Administrator from both the authenticated and non-authenticated instances

B1 B2

1.15 The system will allow for a forced-password change after a specified period of time, which will be configured in the system

B1 B2

1.15.1 The system will notify the user of a need to change

passwords via the preferred communication method selected

B1 B2

1.16 The system shall require passwords to be based industry

best practices, currently 8 characters long including 1 special character and 1 number.

B1 B8

1.17 The system shall provide access to a password retrieval

option from the log-in screen

B1 B2 B8

1.19 The system shall provide a logout function B2

1.20 The system shall log the time and date of each user login B6

1.21 The system shall automatically log the user out after a

configurable amount of time.

B8

2.0 User Profile

2.1 The system shall allow the user to set their profile

information privacy levels

B9

2.2 The system shall require a user to specify a preferred

method of communication to which messages and notifications will be transmitted, with options to include:

Email (specifying which address) or SMS

B1 B2

2.3 The system shall support multiple email addresses

associated with a user profile and allow for a default email address to be specified.

B1 B2

2.4 The system shall associate a user record with a primary

organization

B2 B3

2.4.1 The system shall enable a site administrator to associate a user record with a secondary organization

B2 B3

2.5 The system shall allow a user to edit their user profile B2 B3

2.6 The system shall maintain a user profile that contains the following fields:

- Preferred Language

- Family Name

- Given Name

- Middle Name

- Country of Residence

- Email Address

- User Name

- Short Biography

- Telephone Number

- Primary Organization

- Secondary Organization

- Group Associations

- Areas of Expertise

- Areas of Interest

- User Name

- Other IDs (Facebook, LinkedIn, etc.)

- Photo

B2 B3

2.7 The system shall allow site administrators to edit a user profile

B2 B3

2.7.1 The site administrator shall be able to edit the following user profile fields: all fields from 2.3.1

B2 B3

2.8 The system shall confirm the successful update of a user

profile

B2 B3

2.9 The system shall allow a user to change their password

using the following process:

1. The user will enter a new password

2. The user will re-enter a new password for confirmation

3. The user will submit the change request

B2 B3

2.9.1 The system shall confirm the successful update of a

password

2.9.2 The system shall alert the user if the passwords entered don't match

2.9.3 The system shall alert the user if the passwords entered don’t meet the password requirements (See Req. 1.15)

2.10 The user shall be able to view details for completed

events, including:

Event Title Event Description Dates

B2 B3

2.10.1 The user shall be able to view the following details of an events on their profile:

Link to Event;

Event Name;

Event Date;

The user shall be able to view the following details when linking to an event from their profile:

Link to Event;

Event Name;

Event Date;

Description.

B2 B3

2.11 The system shall enable users to update areas of

expertise information

B2 B3

2.11.1 The system shall maintain a set of areas of expertise from which a user can select all that apply to them

B2 B3

2.11.2 The system shall provide the following topics related to areas of expertise:

Anti-Corruption Border Security and Control Building Partnership Capacity Civil Military Emergency Preparedness & Planning Civil-Military Relations Command, Control and Communications Counter Terrorism Cyber Security Defense Resources Management Disaster Management & Response Energy Security Environmental Security Global Health Human Rights Human Trafficking Humanitarian Assistance International Law Maritime Security and Piracy Nuclear, Biological, Chemical Defense Organized Crime Peace and Conflict Development Peacekeeping Public Diplomacy Reconstruction and Stability Operations Security Studies Small Arms and Light Weapons Weapons of Mass Destruction

B2 B3

2.11.3 The system shall associate identified SMEs with related areas of expertise

B2 B3

2.11.4 The areas of expertise topics shall be searchable by topic title and description

B2 B3

2.11.5 Users shall be able to nominate themselves as SMEs with the topics

B2 B3

2.11.6 The areas of expertise topics shall provide a description of the topic

B2 B3

2.11.7 The system Areas of expertise shall have a time lines field delineating when the experience was gained and when it ended

B2 B3

2.11.8 The systems shall allow end-users to specify degree of mastery setting with each area of expertise topic including Familiar, Experienced, and Expert

B2 B3

2.11.9 The user profile shall include Areas of Expertise fields, including: Education, Training and Certification, Relevant Experience and Activities, and Employers (Agencies, Depts., Working Groups, etc.), Biography, County of Interest, Contact Information (Email, Telephone, SMS)

B2 B3

2.12 The system shall allow users to define areas of interest to be associated with the user profile

B2 B3

2.12.1 The system shall provide a set of standard areas of

expertise, including: same list from 2.9

B2 B3

2.12.2 The system shall allow system administrators to update the set of predefined areas of expertise.

B2 B3

2.13 The system shall allow site administrators to export profile records as a comma separated value file (CSV)

B2 B3

2.14 The system shall allow for bulk adding of users already

associated with a course to be added to a related event

B2 B3

2.15 The system shall automatically add a user to their defined Country of residence upon upload or data entry

B4

2.16 The system shall allow site administrators to view updates to individual user profiles.

B2 B3

2.16.1 The system shall allow site administrators to view updates to a user profile as a page within the system

B2 B3

2.16.2 The system shall display a list of fields that have been changed on the profile tracking page

B2 B3

2.16.3 The system page shall include the field types and names that were changed and not the actual data that was changed.

B2 B3

2.16.4 The system page shall include the username B2

B3

2.16.5 The system page shall include a link to the user's profile B2 B3

2.17 The system shall allow a user to manage privacy settings for their user profile. Options for settings will including:

visible to everyone, visible to my friends and groups, visible to my friends only, and visible to me only

B9

2.18 The system shall one email addresses with a user profile:

one external and one GlobalNET

B4

2.19 The system shall associate up to three (3) phone numbers with a user profile

B4

2.20 The system shall store each user's password in an

encrypted format for authentication purposes.

B8

2.20.1 The system shall encrypt passwords in accordance with

FIPS 140-2 standards

B8

2.21 The system shall allow site administrators to add a red flag status to a user profile

2.21.1 The system shall enable site administrators to limit access for a red flagged account

B2 B3

2.21.2 The system shall limit access by restricting a user's ability to post a comment, add content, or add an associate.

B2 B3

2.21.3 The system shall enable site administrators to delete a red flagged account

B2 B3

2.21.4 The system shall allow user profiles with a red flagged status to be viewable by site administrators only

B2 B3

2.21.5 The system shall provide a free text area for site

administrators to add an explanation of the red flag status

B2 B3

2.22 The system shall send notifications to users who have not updated their profile for six, consecutive months

B2 B3

2.23 The system shall provide a free text field for a salutation in the user profile

B4

2.24 The system shall archive a user's profile after 6 months from the date of death

B9

2.25 The system shall provide the ability to assign roles and permission to users so that different groups and user types can leverage the platform

B6

2.26 The system shall allow for role-based permissions and

privileges.

B6

2.27 The system shall provide for the ability to define new user roles

B6

2.27.1 The system shall allow site administrators to define new user roles

B6

2.27.2 The system shall allow site administrators to define

permissions for user roles

B7

2.28 The system shall generate a Areas of Expertise report for site administrators

B5

2.28.1 The Areas of Expertise report shall contain the following fields: Username, Contact Information, Country of Interest, Areas of Expertise, Availability, Biography, Primary Organization

B5

2.28.2 The Areas of Expertise Report shall display SME

Availability, including: Contact me directly, Contact my Institution, Not Available

B5

2.28.3 The system shall allow site administrators to both

download to an MS Excel compatible format or print, from the interface in a print friendly format, the Areas of Expertise report.

B5

2.29.2 The system shall allow administrators to designate users as SMEs

B2 B3

2.29.3 The system shall allow site administrators to nominate users as SMEs

B4

2.29.4 The system shall allow users to self-nominate as a SMEs B4

2.29.4.1 The system shall require self-nominations to be approved by a designated authority.

B8

2.29.7 The system shall send notification to users when they

have been approved a SME status

B4 B9

2.30 The system shall display a user's associates B4

2.31 The system shall reveal only non-confidential fields in a user search results set B9

2.32 The system shall enable site administrators to view full user profile

B8

2.34 The user shall be able to store their language preferences within their user profile.

3.0 Communications

3.1 The system shall provide the means for a user to chat with another user

B4

3.2 The system shall provide the means for multiple users to

chat with each other.

B4

3.3 The system's Chat feature shall default to the language

specified in the user profile

B9

3.4 The system shall automatically log all chat sessions and

be able to publish chat sessions with all users consent.

N/A

3.5 The system shall automatically sign the user in to chat

upon login to the system

B4

3.5.1 The system shall allow the user to turn off the automatic sign in to chat upon login to the system

B4

3.6 The system shall allow the user to change his status to

ensure that chat system does not allow others to engage the user during the current session.

B4

3.7 The system shall allow the community administrator to turn off and on chat capabilities for his community.

B4

3.8 The system shall provide ability for the chat receiver to view their chat text into another language (English, Arabic, French, German, Russian, Spanish and Portuguese)

B4 B9

3.9 The system shall provide the ability for a user to view a translation of others' chat text in their language of choice

B4 B9

3.10 The system shall allow sending of blast messages in any

official GlobalNET language

B9

3.11 The system shall allow the user to hyperlink to content

within the chat

B1 B3 B6

3.12 The system shall support accent characters B1

B6

4.0 Groups

4.1 The system shall provide for communities of interest, also known as groups B4

4.2 The system shall allow authorized user to create a group B4

4.3 The system shall provide the ability for authorized users to approve user-created groups before they are made available

B4

4.4 The system shall restrict group creation per roles and

permissions (based on individual organization/site policy and procedures)

B4

4.5 The system shall have parent and child relationships

amongst groups

B4

4.5.1 The system shall require a user to manually join or request to be added to a child group

B4

4.5.2 The system shall automatically enroll a member into the groups parent group unless and administrator changes the behavior.

B4

4.5.3 The system shall give the option for a group member to

submit a request for group invitation into that group's parent group

B4

4.6 The system shall allow for development of group templates to be reused for alumni chapters, topics of interest, courses, country groups, events, and other types of groups

B4

4.7 The system shall allow users to view the name and

nonmember view of all groups that are not hidden and which they are authorized to view

B4

4.8 The system shall allow group members to invite other

users into an open group

B4

4.8.1 The system shall send a notification to the invitee with the group invitation

B4

4.8.2 The system shall notify the end user by the preferred

method and language defined by the user (e.g., via the user profile)

B4

4.9 The system shall notify the group manager (or other

authorized user) when a user invites another user into a non-open group

B4

4.1 The system shall allow only group managers (or other

authorized user) to invite other users into a closed group

B4

4.10.1 The system shall allow group members to send requests

to the group manager (or other authorized user) for the invitation of another user(s) into the closed group

B4

4.10.2 The system shall notify the invitee upon approval of their closed group invitation

B4

4.10.3 The system shall notify the requester upon rejection for closed group invitation

B4

4.11 The system shall send any group request notification in the preferred language of the recipient

4.12 The system shall allow the group manager (or other

authorized user) to perform bulk acceptance transactions of potential group members

B4

4.12.1 The system shall allow the group manager (or other

authorized user) to approve a subset of potential group members at once

B4

4.12.2 The system shall allow the group manager (or other

authorized user) to reject a subset of potential group members at once

B4

4.12.3 The system shall allow the group manager (or other

authorized user) to approve all potential group members at once

B4

4.12.4 The system shall allow the group manager (or other

authorized user) to reject all potential group members at once

B4

4.13 The system shall allow users to become members of

groups from all organizations, as permitted by the organizations

B4

4.14 The system shall provide closed groups which shall

require group manager approval to join

B4

4.15 The system shall allow the group manager (or other

authorized user) full moderation of moderated or closed groups

B4

4.16 The system shall notify the group manager and any

additional designated authorized user when a user requests membership in a restricted group

B4

4.17 The system shall notify the requester upon group manager rejection for restricted group invitation

B4

4.17.1 The system shall notify the requester upon group manager approval for restricted group membership

B4

4.18 The system shall provide the capability to create open

groups, for all users to join

B4

4.19 The system shall allow all users to freely join open groups B4

4.19.1 The system shall allow all group members to freely leave open groups B4

4.19.2 The system shall allow all group members to freely

participate in open groups

B4

4.19.3 The system shall allow users to add taxonomic terms to users, events, courses, and groups

B4

4.20 The system shall require a group manager role for each

group

B4

4.21 The system shall support having multiple group managers

for a group

B4

4.22 The system shall allow group managers to moderate or

edit any posted content within a group

B4

4.22.1 The system shall log anytime a group manager, member, or other authorized user edits content

B4

4.22.2 The system shall provide an option to notify group

members when an item has been edited by their group manager

4.23 The system shall allow group managers (and/or other

authorized user) full moderation capabilities for all activity in the group

B4

4.24 The system shall allow group managers (or other

authorized user) to remove group members from the group

B4

4.24.1 The administrator shall notify the removed user of their removal

B4

4.24.2 The administrator shall require the group manager (or

other authorized user) to provide a description for the reason of the user's removal

B4

4.25 The system shall provide a dashboard page for groups B4

4.26 The group's dashboard shall provide group summary

information, links, group content, events, and group messages and provide access to view group members

B4

4.26.1 The system shall provide a way for a group managers (or other authorized user) to position or reposition content (e.g., blocks, feeds, links) for display on the group dashboard, in accordance with site settings and permissions

B4

4.27 The system shall provide a way for templates to be set up for different group types, including but not limited to:

Course, class, country group, alumni group

B3 B4 B6

4.28 The group's dashboard shall provide a prominent

announcement area located in the top center section of the page.

B4

4.29 The group's dashboard shall provide the capability to view all group members per permissions and privacy settings

B4

4.3 The system shall provide the capability to sort groups B4

4.31 The system shall provide the capability to filter groups by topic and other criteria e.g., as in a faceted system B4

4.32 The system shall provide the associated nation next to the user's name while viewing all group members

B4

4.33 The system shall have threaded forums B4

4.33.1 The system shall provide the capability to easily reply to a comment in a thread B4

4.34 The system shall allow users to post comments

anonymously. Administrators shall be able to view these user's information. The option to post anonymously shall be center-specific.

4.35 The system shall provide an easy way for authorized users to post comments on content available in a group

B4

4.36 The system shall provide group managers and other

authorized system roles to organize or reorganize discussion topics

B4

4.37 The system shall allow group members to add content to

their group

B4

4.38 The system shall allow group members to edit their posted content in their group

B4

4.39 The system shall allow users to upload files including

photos, images, PDFs, video, and documents to groups

4.39.1 The system shall provide a way to compress large image files when they are uploaded to a group

B4

4.39.2 The system shall allow users to organize photos, images, PDFs, URLs, etc., and documents into collections within a group

B4

4.40 The system shall allow multi-user chat within a group B4

4.40.1 The system shall allow multiple chat rooms for a group B4

4.41 The system shall allow group members to toggle

notifications for new content or comments within the group

B4

4.42 The system shall provide RSS feeds within a group B4

4.43 The system shall notify the group manager (and any other designated authorized user) when a group member leaves the group

5.0 Events

5.1 System shall allow a user to select a topic or topics to be associated to an event

B2 B3

5.2 The system shall provide a way for the site manager or

administrator to designate other authorized users to add, create, edit, and/or delete events on the organization/site calendar

B3 B4 B6

5.3 The system shall provide a way for the site manager and

other authorized users to create, add, edit, and delete events

B3 B4 B6

5.4 The system shall provide a way for authorized users to

select an event type when creating, editing, or adding an event (course, class, seminar, etc.)

B3 B4 B6 B7

5.5 GlobalNET shall provide all groups and events with the

option to have a calendar

B3 B4 B6

5.6 The system shall provide the ability for a site manager or other authorized users to save an event as a draft before making it public and inviting users

B3 B4 B6 B8

5.7 The system shall provide a way for site managers and

other authorized users to preview events before posting

B3 B4 B6

5.8 The system shall designate official fields as required for global events that event creators must complete

B8

5.9 The system shall provide ability to associate one or more countries with an event

B2 B3

5.10 The system shall provide a way for the association of

objective and policy with an event

B5

5.10.1 Objectives and policies should be able to be added ad hoc by authorized users

B9

5.11 The system shall provide the ability to associate

multimedia content with content types.

5.11.1 The system shall provide the ability to upload bulk content and associate it with an event (e.g., multiple photos)

B2 B3

5.11.2 The system shall provide the ability to tag content during bulk upload

B2 B3

5.12 The system shall provide the ability to create reoccurring events

B2 B3

5.13 The system shall provide a way to import events in csv

format

B3 B6

5.14 The system shall provide a way for Events to be

associated with one or more groups

B2 B3

5.15 The system shall provide a way to flag events as Global

Center events for display on the Global Center organization's calendar.

B2 B3

5.16 The system shall provide the ability to associate events with more than one organization

B2 B3

5.17 The system shall provide a way for authorized users to

nominate an event to be a global event, in order for it to be pushed to the Global Center calendar

B2 B3 B6

5.17.1 The system shall provide a way for users to nominate an event to be a public event in order for it to be pushed to the public view of an organization's site calendar

B2 B3 B6

5.17.2 The system shall require staff approval for events

nominated as public or global, before posting

B2 B3 B8

5.18 The system shall provide a way for staff administrators and other authorized users to specify whether they must approve events imported from other GlobalNET sites before the imported events are posted to the calendar

B2 B3 B6

5.19 The system shall provide a way for the Event Calendar to be downloaded in a standardized common calendar format and in MS Outlook format

B2 B3

5.20 The system calendar shall be able to send event invite

emails in a standardized common calendar format (e.g., iCal) readable by MS Outlook

B1 B3 B6

5.21 The system shall provide a way for an Event Calendar to

pull event data from Microsoft Outlook calendars already maintained by GlobalNET organizations

B3 B6

5.22 The system shall provide the ability to send event

invitations from the system

B1 B3 B4

5.23 The system shall provide a way for site manager and other authorized users to add and/or remove invitees from events

B3 B6

5.24 The system shall provide a way for the site managers and other authorized users to reuse an invitee list

5.25 The system shall provide a way for site managers to send event invitations to GlobalNET users

B3 B6

5.26 The system shall provide a way site managers to send

event invitations to non-GlobalNET email addresses

B3 B4 B6 B9

5.26.1 The system shall provide a way for staff administrators and other authorized users to specify whether they must approve events imported from other GlobalNET sites before the imported events are posted to the calendar

B3 B4 B9

5.27 The system shall provide a way for recipients of event

invitations to RSVP

B3 B4 B5

5.28 The system shall provide a way for users to change their RSVP status as needed

B3 B9

5.28.1 The system shall provide the option to request explanation of RSVP changes

B3 B6 B9

5.28.2 The RSVP change explanation shall provide a predefined set of options for the invitee to select from, plus an ability to provide an "other" explanation

B3 B4 B5

5.29 The system shall provide a way for the event manager to

control whether event RSVP status information (i.e., who is attending) is available to all users, event invitees or authorized users/administrators only

B3 B6 B8

5.30 The system shall provide a way for designated users to

view the RSVP status of event invitees

B3 B6

5.31 The system shall support export capabilities of RSVP data into CSV and Excel formats

B3 B6

5.32 GlobalNET shall provide the ability to record and track who has accepted and did or did not actually attend

B3 B5 B6

5.33 The system shall provide the option to notify confirmed

attendees of event changes immediately as soon as changes are posted

B2 B3

5.34 The system shall provide an event description as part of a detailed event display

B2 B3

5.35 The system shall provide the ability to have event

materials and other content including downloadable files within an event

B2 B3 B6 B9

5.36 The system shall provide a way to display or access an

event schedule on an event page

B2 B3

5.37 Event details pages shall provide a contact link to

someone who can assist when a user needs help with an event

B1

5.38 The system shall support manual messaging to event

attendees.

B3 B6

5.39 The system shall provide the ability to send surveys to

event attendees

B3 B5 B6

5.39.1 The system shall provide the option to remind users to complete event surveys until finished

B3 B6

5.40 The system shall provide the ability to ask non-attendees who accepted the invite, why they did not attend

B3 B6

5.41 The system shall provide an area for event managers to

write a text and images event summary upon event conclusion

B2 B3 B6

5.42 The system shall provide ability to generate a group or

groups out of an event after the event has concluded

B2 B3 B4 B6

5.43 The system shall provide the ability to add attendees after an event has occurred

B1 B5 B6

5.44 The system shall include all added attendees in all follow up actions and attendance reporting

B1 B5 B6

5.45 The system shall provide the option to provide one or more pre-event reminders to the invitees, as reminders of the event (via the users' preferred contact medium)

B2 B3 B4 B6

5.46 The system shall provide a way for the users to select

whether they receive event alerts

B9

5.47 The system shall provide customizable event

alerts/notifications to designated users when a country has not had any events within a designated period of time

B5 B6 B9

5.48 The system shall provide ability for users to see events overlapping in time and location

5.49 The system shall provide the ability to create child groups (subgroups) /events within an event, to support the discussion and collaboration of sub-topics

B2 B3 B4

5.50 The system shall provide a way to associate content with specified child groups/events within an event and its associated group

B2

5.51 The system shall provide ability to filter events by criteria including:

GlobalNET organization (e.g., APCSS)

COCOM

Country Event Type Topic Date or date range Day/Week/Month/Year Contact Person

B2 B3 B4 B6

5.52 The system shall provide the ability to download events

into a CSV file and Excel formats

B2 B3 B4 B6

5.3 The system shall allow group managers (and/or other

authorized user) to add events or create new events on their group event calendar

B4

5.4 The system shall allow group managers (or other

authorized user) to remove events from their group calendar

6.0 Survey

6.1 The system shall allow users to create a survey B4/B5

6.2 The system shall allow users to modify each survey B4/B5

6.3 The system shall allow users to create a survey off of an existing survey B4/B5

6.3.1 The system shall allow users to duplicate only those

surveys to which they have access

B4/B5

6.4 The system shall allow for polls to rank order choices or to choose one choice from a group

B4/B5

6.5.1 The system shall allow survey and poll restriction based on group, country, user roles, events, courses

B4/B5

6.5.2 The system shall by default set the survey and poll to be open to all users

B4/B5

6.5.3 The system shall allow users the capability to modify the access restriction on a live survey or poll

B4/B5

6.5.4 The system shall allow users the capability to modify the access restriction on an archived survey and poll

B4/B5

6.5.5 The system shall allow users to modify access restriction based on group, country, user roles, events, courses

B4/B5

6.5.6 The system shall allow access restriction levels: View only, Participant, Hidden

B4/B5

6.6 The system shall allow users to manually archive surveys

and polls

B4/B5

6.6.1 The system shall by default archive a survey and poll once it has been closed

B4/B5

6.6.2 The system shall allow for manual archiving of surveys

and polls before survey's and poll's close date

B4/B5

6.7 The system shall allow users to manually re-open surveys B4/B5

6.8 The system shall provide a unique identifier for each

survey and poll

B4/B5

6.8.1 The system shall provide a unique identifier for each

individual survey question

B4/B5

6.9 The system shall support the creation of one survey in any supported language

B4/B5

6.9.1 The system shall allow the user to select the language

option available for the survey, if applicable.

B4/B5

6.9.2 The system shall by default set the survey and poll

language to the user's default language selection if the survey is available in that language

B4/B5

6.9.3 The system shall provide aggregated results of all the

survey responses regardless of language

B4/B5

6.10 The system shall allow the user to select groups, and/or individuals, or individuals that attended a course or event as the survey respondents (the user)

B4/B5

6.10.1 The system shall allow the user to generate an email to all the users with a message and link to start the survey

B4/B5

6.11 The system shall allow the user to set an automatic start and end (close) date for survey responses

B4/B5

6.11.1 The system shall allow the user to manually close the

survey

B4/B5

6.11.2 The system shall allow the user to delete the survey and it's responses

B4/B5

6.12 The system shall allow the user to save survey responses before submitting

B4/B5

6.12.1 The system shall allow the user to review survey

responses before submitting

B4/B5

6.12.2 The system shall allow the user to edit survey responses before submitting

B4/B5

6.13 The system shall by default generate an HTML report of

survey results

B4/B5

6.14 GlobalNET survey results page will display the number of users surveyed by region

B4/B5

6.15 The system shall provide survey statistics on number of

respondents, number of respondents that completed the survey, TBD

B4/B5

6.15.1 The system shall provide survey statistics on number of respondents versus requests for the survey originator/owner

B4/B5

6.16 The system shall only allow approved users and groups to view survey results

B4/B5

6.17 The system shall allow the user to view responses while

the survey is open

B4/B5

6.18 The system shall allow the survey creator to have option to hide survey results while the survey is still open

B4/B5

6.19 The system shall allow the survey creator to have the

option to display survey results to users at close of the survey

B4/B5

6.2 The system shall allow the survey creator to have the

option to display survey results to other Centers at the close of the survey

B4/B5

6.21 The system shall archive survey results B4/B5

6.22 The system shall allow approved users to define when

surveys will be archived B4/B5

6.23 The system shall allow approved users to archive surveys before defined expiration time

B4/B5

6.24 The system shall display a link to available surveys on the users dashboard

B4/B5

6.24.1 The system shall remove survey link from the user

dashboard after the survey is completed

B4/B5

6.25 The system shall provide print availability of a survey in print friendly format.

B4/B5

6.26 The system shall allow the user to create a quick poll B4/B5

6.27 The system shall display the results of the poll to the voter B4/B5

6.27.1 The system shall restrict the voter from viewing results prior to voting

B4/B5

6.28 The system shall allow the user to close the poll B4/B5

6.28.1 The system shall allow the user to set a close date B4/B5

7.0 Content Management System (CMS)

7.1 The system shall allow authorized users to create and

author content

B3

7.2 The system shall provide clear data entry forms for

authoring all types of content.

B3

7.3 The content authoring forms shall include a What You See

Is What You Get (WYSIWYG) HTML text editor

B3

7.3.1 The WYSIWYG authoring environment shall not require

the user to know HTML or any other form of scripting language

B3

7.3.2 The WYSIWYG authoring environment shall allow the user

to format text to bold, italics, underline, cross-out, subscript, and superscript

B3

7.3.3 The WYSIWYG authoring environment shall allow the user

to change the color of the text

B3

7.3.4 The WYSIWYG authoring environment shall allow the user

to provide color highlighting of a selection of text

B3

7.3.5 The WYSIWYG authoring environment shall provide the

user with a predetermined set of colors for text colors and highlight colors

B3

7.3.6 The WYSIWYG authoring environment shall provide the

user with a colorpicker tool

B3

7.3.7 The WYSIWYG authoring environment shall provide the

user with the capability to format text in bullets

B3

7.3.8 The WYSIWYG authoring environment for formatting text

with numerical bullets

7.3.9 The WYSIWYG authoring environment shall allow the user

to set paragraph formatting to align left, center, and right

B3

7.3.10 The WYSIWYG authoring environment shall allow the user to increase and decrease text size

B3

7.3.11 The WYSIWYG authoring environment shall allow the user to vertically align the text to top, middle, and bottom

B3

7.3.12 The WYSIWYG authoring environment shall allow the user to increase indent and decrease indent for a selection of text

B3

7.3.13 The WYSIWYG authoring environment shall provide the

user with a table designer

B3

7.3.14 The table designer shall allow the user to designate the number of columns and rows the table should have

B3

7.3.15 The WYSIWYG authoring environment will allow the user

to add or remove columns and rows as they need

B3

7.3.16 The WYSIWYG authoring environment shall not allow the

user to select fonts.

B3

7.3.17 The WYSIWYG authoring environment shall allow the user to hyperlink a selection of text

B3

7.3.18 The WYSIWYG authoring environment shall allow the user to insert an image

B3

7.3.19 The WYSIWYG authoring environment shall allow the user to insert an image from a selection of images in that user's group

B3

7.3.20 The WYSIWYG authoring environment shall allow the user to select a document to hyperlink to from a selection of documents based on the user's permissions.

B3

7.3.21 The WYSIWYG authoring environment shall allow the user to copy a selection of text

B3

7.3.22 The WYSIWYG authoring environment shall allow the user to paste a selection of text

B3

7.3.23 The WYSIWYG authoring environment shall allow the user to copy a selection of text from an external source and paste into the content editor

B3

7.3.24 The WYSIWYG authoring environment shall allow the user to link to another content item in the system

B3

7.3.25 The WYSIWYG authoring environment shall allow for copy and paste functionality from external applications (MS Word, Excel, PDF, Power Point, HTML pages) without scripting or code appearing.

7.4 The system shall support accent marks and characters

from other languages

B3

7.5 The system shall allow a user to save a draft of their

content

B3

7.5.1 The system shall allow a user to preview a draft of their content

B3

7.5.2 The system shall not allow other users to view the draft of a user

7.6 The system shall provide a capability to compare changes

to content

B3

7.7 The system shall provide version control over all published and posted content

B3

7.7.1 The system shall identify the user who made edits to

content

B3

7.7.2 The system shall identify the date and time the user made edits to content

B3

7.7.3 The system shall allow an authorized user the ability to revert back to a previous version of content

B3 B6

7.7.4 The system shall allow a user to reject changes to content by first reviewing changes and then reverting back to an earlier version if the changes are not desired.

B3 B6

7.8 The system shall manage all comments from users to the

associated content item

B3 B6

7.9 The system shall provide the capability for users to reply to comments

B3 B6

7.10 The system shall provide the ability to host photo albums B3

7.10.1 The system shall allow the user to provide captions to individual photos B3

7.11 The system shall provide the ability to upload photos in bulk

B3

7.12 The system shall provide an icon to indicate that a link is external to the system. The icon will be explained in the help documentation.

B3

7.13 The system shall have some form of visual disclaimer for content not posted by the center. (IE. A symbol next to "official" center postings or a specific color for center postings. Possibly, everyone's posts are in black but Center official have blue colored posts and comments". )

B3

7.14 The system shall associate the content with the creator B3

7.15 The system shall allow the user to easily report

inappropriate content to the site administrator or group manager

B3

7.16 Notifications that result from a user reporting inappropriate content should be sent by the system in each user's preferred method of communication.

B3

7.17 The system shall only allow authorized users to modify

posted and published information within the system

B3

7.18 The system shall provide options for organizations and

sites to designate 1 or more authorized users to approve moderated content before it is posted live

B3

7.19 The system shall provide the ability to create and publish timed and repeated announcements

B3

7.2 The system shall allow the workflow to pass ownership of

a content item to another user

B3

7.21 The system shall allow all content posted to be printed or formatted for print

B3

7.22 The system shall only allow authorized users the ability to export content

7.22.1 The system shall allow the authorized users to identify the users and give them access to export content

B3

7.23 The system shall allow authorized users or the content

author (if a user) to identify copyrighted material

B3

7.24 The system shall allow embedding of video and provide a

streaming player for common web formats.

8.0 Search

8.1 Search will conform to access controls inherited by the

user level. IE fields a user cannot see cannot be search on (results for such fields will not be displayed).

B9

8.2 The system's search shall include searching and providing results for content and users across all GlobalNET sites (within constraints of established information access and privacy policies, and user's authorization to view)

B3 B4

8.3 The system shall provide for full-text search capability B3 B4

8.4 The system shall support Boolean "AND" search queries B3

B4

8.5 The system shall support Boolean "OR" search queries B3

B4

8.6 The system shall provide keyword search that

indexes/searches all content types, and indexes/searches all content fields, metadata, and tags

B3 B4

8.6.1 The system's keyword search shall include Event titles and descriptions, Group titles and descriptions, and posted URLs (links to other websites)

B3 B4

8.6.2 The system's keyword search shall include

indexing/searching all fields in user profiles

B3 B4

8.6.3 The system's keyword search shall include

indexing/searching all user comments, blogs, and other personal content the searching user is authorized to view

B3 B4 B9

8.7 The system shall provide a way for keyword and user

search results to be refined by predefined filters/facets (based on the attributes of the result set)

B3 B4

8.7.1 The predefined search results filters/facet system shall have filter sets for four (4) main categories of searches:

User, Document, Event, Discussion

B3 B4

8.7.1.1 The predefined filters for the search category "User" shall be: organization, country, topics of interest

B3 B4

8.7.1.2 The predefined filters for the search category "Document" shall be: document type, country (document's topic), topic of interest, date range (of document creation), author, language

B3 B4

8.7.1.3 The predefined filters for the search category

"Discussions" shall be: topics of interest, date, author

B3 B4

8.8 Types of personal content shall be included as content

type filter options (e.g., comments or user-generated content)

8.9 The user-related search results filters shall include: Filter by: Organization, Country of Residence, Nationality, Areas of Expertise, Interests, Courses Attended, Date of Community Membership and Date of Birth.

B3 B4

8.10 The system shall provide a way to filter a user's associates by expertise. (IE. I want to filter to show all associates who are experts in Small Arms)

B3 B4

8.11 The system shall display a profile image, when added and reviewed as per the User Profile requirements, in the search results display

B3 B4

8.11.1 The systems shall display a standard, placeholder image in the search results display if a user has not uploaded a picture

B3 B4

8.12 System search results that include files shall include the titles of the files

B3 B4

8.13 The system shall provide a way for the user to export

search result sets into CSV format

B3 B4 B9

8.14 The system shall default to searching using the user's

preferred language and shall return results in that language where results are available in that language

B3 B4 B9

9.0 Personal Dashboard

9.1 The system shall default to either the user's "dashboard" or community page per community policy upon successful authentication

B2 B3 B4

9.2 The personal dashboard shall provide access to the user's:

Event Calendar, Group Membership, Announcements, Associate List, Chat, Private Messages, News Feeds, and Bookmarked pages

B2 B3 B4

9.3 The personal dashboard shall display links to all the

organizations with which a user is associated

B2 B3 B4

9.4 The personal dashboard shall provide access to the

MERLN resource to eligible users

B2 B3 B4

9.5 The system shall present the dashboard in the person's

selected default language

B2 B4 B9

9.6 The system shall allow site administrators to post

Announcements to be displayed on or accessed via users' personal dashboards

B2 B3 B4

9.6.1 The personal dashboard shall allow the user to hide

announcements (e.g., minimize their container other method) once viewed

B2 B3 B4 B9

9.7 The personal dashboard shall provide the ability to access existing groups, add groups, and remove groups

B2 B3

9.8 The personal dashboard shall display the current

courses/classes in which a user is enrolled

B2 B3 B4

9.9. The personal dashboard shall display the current events

for which a user is registered

B2 B3 B4

9.10 The personal dashboard shall display the registered

events in a different manner than non-registered ones (e.g., public events that might be displayed on a combined calendar)

B2 B4 B6

9.10.1 The personal dashboard shall provide a way for the user to view the upcoming events for which a user is registered

B2 B3 B4

9.11 The personal dashboard shall display the current topics to which a user has subscribed

B2 B3 B4

9.11.1 The personal dashboard shall provide notification of new content for subscribed topics

B2 B4 B9

9.12 The personal dashboard shall remove the status of "New"

once a user has viewed a content item.

B2 B3 B4

9.13 The personal dashboard shall display the content most

recently accessed by the end-user: Friends, Topics, Groups

B2 B3 B4

9.14 The personal dashboard shall display the user's network of contacts (associate list)

B2 B3 B4

9.15 The personal dashboard shall display an option to add

contacts to their network

B2 B3 B4 B9

9.15.1 The personal dashboard shall display an option to remove contacts from their network

B2 B3 B4 B9

9.16 The personal dashboard shall limit the display of the

contacts in the user's network to a predefined number

B2

9.17 The personal dashboard shall display the contacts in the list that are online differently than those that are offline

B2 B3 B4

9.18 The personal dashboard shall allow the user to select the format of display of their network list (e.g., plain text list, text with avatars)

B2 B3 B4 B9

9.19 The personal dashboard shall allow the user to minimize a container of content

B2 B3

9.19.1 The personal dashboard shall allow the user to maximize a previous minimized container of content

B2 B3 B4 B9

9.20 The personal dashboard shall allow access to user profile management

B2 B3 B4 B9

9.21 The personal dashboard shall display a "New" status to be associated with unread messages, and announcements

B2 B3 B4

9.22 The personal dashboard shall provide a way to access the user's student services…