2. Today’s Discussion
• What is Social Collaboration Software?
• What is Open Atrium?
• Who is Open Atrium for?
• Architecture & Structure of Open Atrium
• Demo!
• How to Get Started
Friday, May 31, 2013
3. Open Atrium Lead Architect
Email: mpotter@phase2technology.com
Mike Potter
Drupal.org: mpotter
VP of Strategic Initiatives
Email: kborchert@phase2technology.com
Karen Borchert
Drupal.org & Twitter: karenborchert
Friday, May 31, 2013
9. Why Consider Open Source?
Open source solutions give you a platform you
can extend and customize without fear of lock-
in. They let you build what you need, lose what
you don’t, and keep up with your
organization’s needs and changes to the
collaboration software space.
Friday, May 31, 2013
11. What is Open Atrium?
Open Atrium is a collaboration platform
designed to help organizations manage
their communications, teams, and
knowledge.
Friday, May 31, 2013
12. What does Atrium DO?
Atrium has native features to support knowledge management,
collaboration, and communication.
But through its pluggable framework, can also be extended to
integrate with enterprise-level applications focusing on project
tracking (like JIRA), time tracking (like Harvest, AtTask, or
OpenAir), wikis (like Confluence), and asset management (like
Alfresco and Sharepoint).
Friday, May 31, 2013
13. Features of Atrium 2.0
• Security through access control for individuals, teams, and
organizations
• Discussions: moderated public and private
• Knowledge Management: file storage, collaboration, access
• Simple multi-site or “microsite” implementation
• Mobile ready: responsive themes and layouts
• Pluggable functionality to connect to enterprise-level applications
(custom work, but done as plugins)
• Customizable Layout
Friday, May 31, 2013
14. Open Atrium Can Be Used To...
• Manage projects and clients for a services company
• Meet customers in a discussion forum
• Build an Intranet or manage knowledge with a wiki
• Engage and Inform through a web portal
• Create an extranet for sharing access-controlled information
for business to business knowledge management
Friday, May 31, 2013
16. Who is Atrium For?
Atrium 2.0 is for organizations with
teams, clients, or affiliates who need
a common platform to communicate,
collaborate, and manage knowledge.
Friday, May 31, 2013
17. An Atrium 2.0 Customer may have...
• Multiple chapters, affiliates, franchises, or brands
• Global, Regional, and Local communication needs
• Multiple offices, teams, or branches
• Forums or networks of customers to engage
• multiple campaigns, projects, newsbeats, or aid efforts
• multiple project teams communicating with external clients
Friday, May 31, 2013
45. What You (may) Know about Atrium 1.0
• used by P2 and Dev Seed on some larger intranet projects
(White House, etc)
• useful as a project management tool
• sometimes used for intranets or web portals
• fairly antiquated in its features, doc mgt capabilities, and
extendability
• theme and Features are locked down. D6 is a challenge.
Friday, May 31, 2013
46. How Atrium 2.0 is Different
• Framework-built, Product-use: no single use case, but can
act as a complete solution “out of the box”
• Access Control is Key: changes how users, discussions, and
projects are handled.
• Panopoly-based for ease-of-use
• Plugin-based for extendability
• Theme is light, flexible, responsive (Bootstrap-based)
Friday, May 31, 2013
47. Alpha Release
• Open Atrium 2 Alpha Released on Drupal.org!!
• http://drupal.org/project/openatrium
Friday, May 31, 2013
48. Spaces
• A "Space" is a subset of content
within your Open Atrium instance
that is shared among a collection
of users (members).
• A "Space" can be used for a
Project, Department, Microsite or
any other collection of related
content and people.
• It is an “Organic Group” content
type. (no relation to Spaces
module)
Friday, May 31, 2013
49. Sections
• A "Section" is a collection of
content within a specific "Space"
that is tightly related, or private
to a specific set of users.
• A "Section" can be used for
specific working areas within a
Space, such as a Discussion or
Wiki.
• A "Section" can be assigned
specific access controls to limit
it's visibility.
Friday, May 31, 2013
50. Members
• Spaces have Users assigned to
them called “Members”.
• “Members” can have special
permissions, such as Edit and
Create access.
Space Members
Friday, May 31, 2013
51. Groups
• A "Group" is a collection of users
with related roles or interests than
span across multiple Spaces.
• A "Group" can represent a
specific company or organization,
or it can represent a common
role, such as "project managers"
or "developers".
• Groups are used to assign access
control to specific Sections within
Spaces.
• Groups are used for Notifications.
Friday, May 31, 2013
52. Teams
• A "Team" is an ad-hoc collection
of users within a specific Space
that share a related purpose.
• "Teams" are used to assign
private access control to specific
Sections within Spaces.
• "Groups" extend beyond
individual Spaces whereas
“Teams” are specific to a
particular Space.
• Teams are used for Notifications.
Friday, May 31, 2013
53. Access Example
• University site split into Spaces for each School:
Humanities, Physical Sciences, Arts, Engineering
• Groups of people for: Faculty, Students, Parents
• Sections within each School Space for Departments:
Course Information, Open Discussion, Private Faculty Discussion
• Teams and Private Sections for:
Department-specific workshops
Friday, May 31, 2013
54. Migrating from Open Atrium 1.x
• No magic way to upgrade sites from Drupal 6 to Drupal 7
• Will create scripts for the Migrate module to help with data
• OA2 only ships with limited Plugins: Discussions, Pages
• Event plugin planned next
• CaseTracker/Issues/Tasks from community
Friday, May 31, 2013
56. DrupalCon Portland
• Live Demo! Tuesday 5/21 9 am: B112 Join Mike
Potter to see Open Atrium and get your questions
answered.
• Come See us for Happy Hour! Demos at 4:00,
beverages at 5:00 every day at DrupalCon at the
Phase2 booth.
• Come hack with us! Hackathon on Friday at
Doubletree hotel. Join Mike Potter to learn how to
create plugins, use Atrium, and extend it for your
organization.
Friday, May 31, 2013
57. Take it for a spin!
getpantheon.com
Friday, May 31, 2013
62. AHRQ
• Consolidate two existing Confluence sites into Drupal
• Data privacy needed for some sections of site
• Discussions, Wiki, Events, FAQs, etc within Spaces
• Approval and comment workflow for some content
• Shared Resources (documents, etc) between Spaces
• Flexible layout needed per Space and on some pages
• User provisioning via LDAP
• Improved Search functionality
Friday, May 31, 2013
65. Open Atrium vs Commons
• Using Commons 3
• Hierarchical Spaces,
• Access control Groups,
• Discussion Forums,
• Wiki pages,
• Layout flexibility,
• WYSIWYG,
• Media (images, video, documents),
• Notifications (push & pull),
• SOLR Search,
• Responsive theme
• Add Plugins for:
• Events
• Calendar (iCal import/export),
• Shared Resources,
• Space Profiles
• Issue Tracking (custom workflow)
• LDAP read/write
• Custom content types
Friday, May 31, 2013
66. Implementation: P2 Products
• Recreated Phase2’s Confluence-based product site in Atrium 2.0
• Major functionality needs were around spaces for each product,
groups for community users vs. P2 people, a place for
discussion (without recreating issue queue) and mostly, a home
for documentation.
• Not a complete migration to this new site, but very, very close.
Usable as a demo; a couple of changes from being ready for
prime-time.
Friday, May 31, 2013
