Slashdot Mirror
Cracking Open the SharePoint Fortress
dreemteem writes with this excerpt from ComputerWorld UK:"SharePoint is a brilliant success, for a couple of reasons. In a way, it's Microsoft's answer to GNU/Linux: cheap and simple enough for departments to install without needing to ask permission, it has proliferated almost unnoticed through enterprises to such an extent that last year SharePoint Sales were $1.3 billion. But as well as being one of Microsoft's few new billion-dollar hits, it has one other key characteristic, hinted at in the Wikipedia entry above: it offers an effortless way for people to put content into the system, but makes it very hard to get it out because of its proprietary lock-in. This makes it a very real threat to open source. For example, all of the gains made in the field of open document standards — notably with ODF — are nullified if a company's content is trapped inside SharePoint." The article offers a slice of hope for getting around that, though, in the form of a new API for Google Sites which can slurp the data back out.
Its great news if *anything* can rescue us from the horror that is Sharepoint.
I've never used a worse CMS system (which is what everyone pretends it is) when really its an online document repository. Don't even start me of Infopath documents being put in there to pretend to give it a forms engine. Its hell.
Thing is, I'm not entirely sure why all the myriad sharepoint sites that have sprung up at our company are so useless, I think its because its so easy to drop another document into another list that you end up with a sprawl of almost-related data, that's then impossible to find. Our admin did try to say that he'd put the search functionality on so it should be easier to find things... but when I searched for one document I received several thousand hits back!
Alternatively it could be because every department has their own sharepoint site, that no-one knows which one to look in for data, so they don't bother using it.
In any case, all the sharepoints here are crap, even the one the admin spent a lot of time on to give it a good sense of organisation.
It requires considerably more iron to run it than Wiki software, and the software licenses are very expensive.
We invested initially in Sharepoint, but can't afford to roll it out for the entire company.
Cheap is the last word I'd use to describe Sharepoint.
Depending on how and what you use Sharepoint for, companies should consider looking at MediaWiki and/or Alfresco for document storage, indexing, processing, sharing, etc.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
Getting content out of SharePoint is blindingly trivial - the web services provided allow you to access all saved versions of documents in document libraries (including wiki pages et al), all user information and all list items.
Grab the information from the web services and do whatever you wish with the resulting data - its neither hard nor hidden, so this story is pointless.
It's actually quite trivial - and getting more so to move your data out of google apps.
See the recent 'data liberation' things they've been doing.
Gmail supports imap. Google Calender supports iCal. Google Docs exports natively to OpenDocument. GTalk uses Jabber and Jingle. Google Chrome is open source, as is Google Wave, Android, and plenty of other things I can't remember offhand.
I haven't really seen that much in terms of lock-in from Google, beyond the fact that they often provide the best implementation -- for example, I don't see how you could lock someone into a search engine, yet Google Search remains dominant because it's actually good.
Can you give me your reason for believing Google would lock people in? Any evidence to back that up?
Don't thank God, thank a doctor!
Why are you so quick to jump to Microsofts defense?
So if you don't gush over Google that means you're jumping to Microsoft's defense?
Bottom line is: avoid proprietary lock-in.
So then why are you using Google's proprietary products then?
What is this lock in? I RTFA and skimmed the linked wikipedia article, and couldn't find any details.
Everything in SharePoint is a list in the database. A calendar is just a list of events with start and end times. A address book is a list of contacts. All you need is some basic SQL, and your information is free.
Documents are also in the database as binary objects. Pulling them out and saving to the local file system can be an exercise for your intern or first year programmer.
The API for SharePoint is fairly well documented. If you wanted to migrate a site from SharePoint to another platform, recreating the look and feel may be a challenge--likely depending on your design skills--but getting your data out will not be.
Can only say one thing to this: http://www.dataliberation.org/
It's an MS web based document management system with CMS capabilties (among other things). Most organizations use it for intranet type sites, but there are many companies that use it to manage their public facing websites as well.
Not that hard to reverse engineer the schema.
This fellow has open sourced a tool to crack it open:
http://blog.dreamdevil.com/index.php/2007/03/13/sharepoint_2003_database_exporter/
The impression I got from just the crap summary was that Sharepoint is idiot easy to install without any planning. This means depending on the individual who sets it up, it'll either work wonderfully for you by enforcing proper tagging and indexing rules or it'll become a pit that simply costs money because you can't find anything important with it.
This is a classic example of Pick any two:
Mod me up/Mod me down: I wont frown as I've no crown
Or at least *copy* the data out of google apps, which is still way better than a lock-in, of course.
O3Spaces
Lenya
SugardCRM
Alfresco
Main pyrus
Nuxeo
There's an actual Read/Write API. It isn't hard. There is no story. Don't be dumb.
Sharepoint is a piece of collaboration based software that Microsoft developed. People can jointly work on documents or data stored on the server, and manage the security within their own niches. The design is primarily to give groups or projects their own space, and then give a lot of control over what happens there to the group leader.
While CMS features were mentioned by another user, they are almost an afterthought or byproduct of the other features, rather than the main purpose of this software. It also happens to SUCK for content management, and it's recommended you get another back end content server to store your Sharepoint managed or created data long term.
Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
While I agree Sharepoint is an abombination, when I've had the misfortune to interact with it (usually, I've needed to do so with various scripts), I found you can actually NET USE Sharepoint as if it were just a normal CIFS drive, and access everything as files.
I don't see what's difficult about getting your documents out again in bulk.
Oolite: Elite-like game. For Mac, Linux and Windows
im not even going to bother googling the stats on that one, but since ive never heard of SharePoint before...
The SharePoint primer for the clueless and lazy:
Microsoft has sold more than 100 million seat licenses since 2001
and is on track to generate $1 billion in SharePoint-related revenue this year.
Ask CIOs about their collaboration strategy, and a good number will start rattling off SharePoint projects. The software's Swiss Army knife approach helps companies create more useful intranets, set up document sharing, offer blogs and wikis, and build a richer online company directory. This boundary-blurring nature is part of its appeal, and can even help in budgeting: IT teams that might not get the nod for document management software have been known to slip SharePoint into the Microsoft Office budget.
General Mills, a longtime SharePoint user, is replacing all its file sharing systems with SharePoint and has begun using it for blogs and wikis, and to automate some workflows. The maker of Cheerios, Häagen-Dazs, and 100 other food brands counts 20,000 active SharePoint users, with more than 1,500 people contributing content on a regular basis.
Can Microsoft Keep SharePoint Rolling? [Nov 1, 2008]
Bottom line is: avoid proprietary lock-in.
So then why are you using Google's proprietary products then?
Google makes it easy to extract your data and put it somewhere else. Sharepoint does not.
The only problem I can see with your statement is that it is completely wrong.
Getting data or files out of SharePoint is dead simple. Aside from a large number of client choices including Windows Explorer, Outlook, Excel, Access, and SharePoint Designer you can create custom interfaces. If you want to create your own interfaces, there is a well documented Web Services API, a well documented RPC API, and over course a set of components if the custom code is running on the server.
The Office apps cost money, but Windows Explorer is Windows, SharePoint Designer is free, and the only things that would stop you from using the programmatic interfaces would be a decision to them to harden security or a lack of knowledge.
Our glorious IT department, guys who just happen to jump to ANYTHING Microsoft releases, moved our intranet to Sharepoint some 6-7 months ago. We are a 1000 man high tech company, producing our own safety critical hardware and software used in civilian and military applications. We have a full-time, large IT department, so we are not just a mom&dad shop who don't know how to turn on the computer.
:-)
Here is our experience with Sharepoint:
- It's SLOW AS HELL. It is mind-blowingly, unbelievably slow. I have NEVER seen such a slow system in my life!
- The search function is un-useable, except for poking fun at results. Rating hits in some xls Documents higher than hits on wiki pages - COME ON, MICROSOFT, EVEN YOU CAN'T BE THAT STUPID!
- Collaboration? Yeah, right - 2 guys from my department worked with 2 other guys in 2 other departments on a document. After 3 days, the damn thing just swallowed the document! No way to roll back, no way to find it (IT also gave up after a few hours of search). It's GONE!
- The WIKI functionality (editor) is awful. Just awful. It changes the spacing between lines at its' liking. No way to fix it, short of turning to HTML mode and repairing it manually, just to see it f*** up again after the next update!
I could go on forever, but I guess you get the picture. MS sure does have some fine products, although I despise their business practice. Sharepoint, however, is NOT one of those fine ones!
OK, I calmed down. Now I go back to work...
we use Sharepoint with non-ms products, it's just not offered out of the box. It's not hard to get set up though.
Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
I don't know about your sharepoint comments, but you're wrong about most everything you said about Drupal. You should have asked me for help.
http://drupal.org/project/webdav
http://drupal.org/project/notify
Also, I don't know what you mean by
as manifested by the fact that you cannot edit things were they are seen by users but rather must work through a back panel.
You click the edit tab, which gives you direct access to edit the page. I don't know how much more direct you want. It's kind of a logical fallacy to say "edit things [as] seen by users". Users cannot edit, therefore you cannot edit *and* see things the way the user would.