Gephi vs. MS SharePoint / SQL

It is well suited for projects that are more discovery related. If this is a one-time project that we create a visual for, this would definitely make sense to use. If this is an ongoing analysis (monthly for example), we might look to another software that we would be able to automate a little further in how the visualization comes together

Incentivized

As I mentioned in my previous answers, MS SharePoint is very useful as a shared drive for the organization and is very easy to manage. It also helps us import data from SharePoint directly into PowerBI for creating reports. According to my understanding, only share link features should be improved.

Incentivized

• In comparison to other tools such as GraphWiz or Circos, Gephi comes with an intuitive, easy-to-use interface that makes it easy to load your data, and quickly start building all sorts of different graphs. There's absolutely no code that needs to be written for either loading or modeling. And without downloading additional plug-ins, Gephi ships with quite a few standard graph models, as well as some "fun" extras such as the Sierpinski triangle, and a variety of force atlas types.
• Most of the layout types (maybe all) are highly configurable, which can make for extremely customized and unique displays of your data. Again, none of this requires the user to write any code. That said, it is possible to script custom functionality for your models, or even update the Java source code yourself, if you feel like getting technical. Gephi builds are available on GitHub, and the developers encourage people to contribute ideas, improvements, and plug-ins.
• There's a plug-in for Gephi that allows for streaming data to update your model. This essentially allows you to create near realtime graphs of your data in motion. This plug-in was by far the biggest reaston we invested time in the product; to create animated data visualizations without exhaustive hours in development.

• Flexible - able to make any changes we would like vs traditional service desk system.
• ROI - We were already using SharePoint for internal intranet, so we are simply getting more use out of licensing we had already committed to.
• Easy to use for end users.

Incentivized

• I (and many others) have had to expand Gephi's memory manually by experimenting with the configuration file. I'm glad it's possible, but it should be easier.
• Gephi sometimes crashes inexplicably and loses your work, so I have developed a habit of explicitly exporting versions of my graphs as csv's, but I think this should be handled automatically in Gephi.
• Because it is prone to crash, ideally, Gephi would help the user manage his/her use, by estimating processing and memory for very large tasks and prompting the user to confirm their requests before executing. Instead, I just tend to avoid certain functions.

• It is hard to setup and nightmare
• It requires a of infrastructure, thus it could be costly because of requirement and licensing required for everything to run smoothly
• If it is not setup and organized properly from the beginning it could be maintenance nightmare
• It is hard to have "test" environment to do patches or similar

Incentivized

While Gephi isn't perfect, it's a powerful tool for mathematical graph modelling that's hard to find in other products, particularly by way of its interface. It grants non-software developers access to a point-and-click way of creating accurate, beautiful visualizations that would normally take hours in other applications. The fact that it allows for live streaming data is also something that's hard to come by, at least for visualization software

This was a long-term buy-in from a corporate perspective, to remain in the SharePoint space. Migration is certainly possible, which is good for planning and having options further out. At this point, the only planned migration is to eventually move the architecture up to SharePoint/SQL 2013. At that point, we will be able to leverage some greater efficiencies, some enhanced content design and management features, and some more current social features. It is well worth a full consideration in any shop looking at a new implementation of or migration to SharePoint (although you will probably be considering 2013 versions or beyond in those discussions), but the platform should be a strong competitor to any alternatives. Realizing the capability of a fully-branded and customized website was not part of the original choice for the architecture at Lincoln, but seeing it implemented and functioning now with this capacity far beyond original expectations has certainly cemented plans to continue using it.

Gephi is very intuitive and the fact that it shows its process helps the user understand what's going on. However, the animation features can really slow it down and there isn't a way to shut them off. Furthermore, the failures on saving mean you frequently have to start over. These problems disrupt the workflow and can be frustrating.

I gave this rating due to MS SharePoint being a big help with our userbase. We have a lot of users that are just old enough to not have much technical skills or they have been in this industry long enough to where they haven't really needed to utilize much technology. MS SharePoint helped us move beyond that barrier without too many bumps and bruises.

Incentivized

I've only had to call in to support on one occasion but they were able to work though our issue and find a solution that did fully resolve the issue in a timely manner. I can't always say the same about support from other companies so it was a refreshing change to have support that did help.

Incentivized

Not implemented in best practice way, there are many customizations

The interactivity in Gephi and the quality of the output figures are impressive. However, the selling point was the fact that we were able to link Gephi into our pipeline using Java's interface. Other products were less customizable and lacking of the sophistication Gephi provided without too much pain during the liking process.

Incentivized

At the time of the two large projects, SharePoint was the enterprise solution so we were required to use that. We have since lobbied the enterprise teams to review and consider Atlassian Confluence and were successful. Confluence is cheaper than Sharepoint which is why we wanted to bring that in. The enterprise has now made Confluence an enterprise solution as an alternative to SharePoint. After using both I think SharePoint has many more add-ins than Confluence. It has much more customization ability than Confluence. SharePoint is not good for mobile readiness. Confluence is so there is a difference that might lead you to Confluence over SharePoint. I would also say that SharePoint is very document-centric and that Confluence has better KM than SharePoint does. even with the use of SQL Server. We were told that we could not use Google Drive even though it had features we liked.

Incentivized

• I have only used the product for education purposes. I will not be the best person to provide details about ROI and business efficiency and customer service. I was personally very excited about the tool and am continuing my work on the tool.

• ROI for ms SharePoint/SQL considering that is the best database engine with excellent features that help you to have all information in your hand.
• Something negative could be license format.
• These are the best relational databases in the market with powerful features that complement your system.

Incentivized