Call us today! +1.651.222.TEAM (8326)

TEAM Takes on the Oracle Social Network Developer Challenge

TEAM Takes on the Oracle Social Network Developer Challenge

Wayne Boerger delivering TEAM's Solution

By: Dmitry Shtulman - Project Manager

Oracle ran a Social Network Developer Challenge (a “hackathon”) at this year’s OpenWorld conference and TEAM was eager to join in.  The goal of the challenge was “to build something that solves a business problem using Oracle Social Network, its Public API and another service or application”.  We were able to put together a team on fairly short notice and, after batting a few ideas around, decided to pursue an integration with JIRA, an issue and project tracking tool used in-house at TEAM.  After getting to know WebCenter Social, we saw immediate benefits that a JIRA integration could bring, primarily due to the fact that JIRA only allows assignment of an issue to one person at a time.  Integrating Social would allow collaboration and issue resolution to happen right from the JIRA Issue interface.

We centered our use case around a fictitious football league whose fictitious referees were on strike.  The replacement refs used JIRA to review calls made in a recent, controversial matchup between the Seattle Seabirds and Green Bay Packels.   Sound familiar? :)

Our plan went as follows:

The What

Integrating JIRA with Oracle Social Network and the Public API on the JIRA issue level.

The Why

We use JIRA at TEAM constantly and while comments within JIRA are available, we often feel it would benefit us to be able to have more collaborative conversations with our peers on certain issues. OSN facilitates that collaboration and problem solving.

The How

We created a JIRA plugin using the Atlassian Plugin Framework to add a new tab to the issue interface. The tab, when activated, pings OSN using the Public API to determine if a Conversation exists for the issue. If no Conversation exists, an interface for creating a new Conversation is shown in the tab. When the interface is used to create a new Conversation for the issue, a call to the Public API is made to perform this task, assigning an External ID to the Conversation that is unique against the JIRA Issue (so the two are linked). Once a Conversation exists, the OSN Social Plugin is used to display the Conversation interface to enable collaboration.

Fig. 1: OSN Conversation tab with a button to view an existing conversation


Fig. 2: Clicking View Conversation button in screen above exposes Social Object Wall

Initially we put a lot of time and effort into a javascript-based integration but couldn’t overcome a cross-browser issue (jsonp and CORS didn’t help us, unfortunately).  When we switched gears to a server-side solution we ran out of time before we could complete the integration.  Although it wasn’t completed in time for the demo, we did generate interest in the concept, at TEAM and externally.  We feel that our concept is close and has some real potential benefits so we will continue pursuing the integration in the coming days and weeks.  We’ll keep you posted on the progress!

TEAM didn’t win the hackathon but with the time constraints of the competition we did pull off an impressive result. If you want to see the Challenge winner’s check them out here.

Tags: integrationInterfaceWebCenter SocialOraclesocial

Enter your email address to receive notifications of new posts by email.

Recent Posts

It's time to put your unstructured data to work Contact TEAM