some valuable grains of salt to keep in mind with SharePoint:
SharePoint 2007: Pointedly unskinnable ~ Authentic Boredom: "...There is a fundamental distinction that must be understood when implementing SharePoint: SharePoint can be used primarily as a CMS or primarily as a collaboration tool. However, try to use it as both in a single implementation and you’ll entangle yourself in a strenuous skinning effort. Let me attempt to explain why..."
Musings on personal and enterprise technology (of potential interest to professional technoids and others)
Saturday, November 10, 2007
SharePoint 2007: Pointedly unskinnable ~ Authentic Boredom
Posted by
dgftest
at
10:43 PM
0
comments
Labels: CMS, SharePoint, Workflow
Sunday, September 30, 2007
Gartner Magic Quadrant for Enterprise Content Management 2007
Nice summary of critical vs. nice-to-have features, in this updated 2007 Gartner Magic Quadrant for ECM:
"... to be included in this Magic Quadrant the vendor must have a content management suite that addresses the following core components. The vendors should have all these capabilities and should have all the components integrated — at least four must be native; other components could be supplied through partners. To be considered for placement in the Leaders quadrant, the vendor must provide all six components natively.
Core document library services (check-in/check-out, version control, document-level security). Advanced capabilities, such as compound document support and content replication, score higher than the minimal library services.
Document imaging repository capabilities. Document imaging consists of two components. The document capture portion can be carried out via native capabilities or else met with a formal partnership with a third-party solution, such as Kofax, EMC Captiva or Datacap. But the vendor must also be able to handle images of scanned documents in the repository as just another file type in a folder, and it must be able to store, retrieve and route them.
Records management — the minimal requirement is the ability to enforce retention of critical business documents based on a records retention schedule. Higher ratings are given for certified compliance with the DoD 5015.2 standard.
Workflow — the minimal requirement is simple document review and approval workflow. Higher points are given to those with graphical process builders, and serial and
parallel routing.
Web content management (WCM) — the minimal requirement is a formal partnership with a WCM provider. Native capabilities score higher than partnerships.
Document-centric collaboration — document sharing, project team support, and support for ad hoc, threaded discussions around documents.
Optional Components
Part of our assessment involves looking at how well each vendor understands evolving requirements and market trends. Electronic forms (e-forms) and digital asset management (DAM) continue to grow in importance, and digital rights management (DRM) is becoming more important as an additional layer of content security. As part of this assessment, we look at the vendor's road map for addressing these optional components as well as integrated document archive and retrieval system (IDARS) and e-mail management/archiving..."
Posted by
dgftest
at
4:13 PM
0
comments
Labels: CMS, ECM, OpenText, RedDot, SharePoint
Wednesday, September 19, 2007
Using Pligg at Work as an easy Corporate Web 2.0 site
OK, would be interesting to hear a Microsoft rebuttal about the Web 2.0 aspects of latest SharePoint-related technology. Meanwhile, fascinating to hear about the "MIMP" vs. "LAMP" implementation:
"Using Pligg at Work as an easy Corporate Web 2.0 site: "For those who do not know the Pligg system is a digg clone site that allows people to submit and vote on stories, we run one as a way to collect social book marks and things we think are important at work, and in our general perusal of the Internet looking for stories and things that influence business. In all it has been a handy way of collecting information as a news sink, that people can later search. We use Pligg as an externally facing social bookmarking site that allows a group of people to manage and upload stories they think are interesting. The site is externally facing as we have telecommuters and other folks who access and use the site. Its purpose is two fold, our customers can upload documents that they think are important, our workers can do the same, and internal/external trusted people can also upload their stuff. We also use it as a test case, to see how many people will stumble over a site like digg clones and adopt them by adding their own stuff, or spam to the system. While it is not a critical system, it does have its uses, and is fairly heavily used by a small core group of folks who search all the major news channels for information that might be of interest to the company....
Not a bad use of corporate Web 2.0 sponsored system, we keep it off the primary network on its own domain, it is not our usual Microsoft technology, meaning the people who run it and maintain it all have to understand LAMP (Linux, Apache, MySQL, PHP) only small variation it is really MIMP (Microsoft Server, IIS, MySQL, PHP) just to confuse people and hackers by the way, it is not something they expect.
Overall though as an initial foray into Corporate Web 2.0, collecting news stories, and voting on them has been a successful experiment. The management has decided that the system is worth keeping, although needs to be upgraded and put into the corporate management system.... "
Posted by
dgftest
at
11:35 PM
0
comments
Labels: Blogging, CMS, ILM, Open-Source, Web 2.0
Thursday, August 30, 2007
SharePoint Deficiencies? "Social Bookmarking Apps Provide a New Knowledge Management Platform", eWeek 8/07
Interesting to see whether Microsoft will finally respond (sounds a bit different from what was suggested in a recent post here, and also different from what one sees on several of Microsoft's own blogs, e.g. the Microsoft Unified Communications Group Team Blog among many others)
Social Bookmarking Apps Provide a New Knowledge Management Platform ( full article ):
"...Microsoft has no social bookmarking solution today. Having just revised SharePoint, the company probably won't release such a package before 2009, said Burton Group analyst Mike Gotta. WSSSearch provides a bookmarking add-on for SharePoint, but representatives for the company did not return eWEEK's requests for information..."
Posted by
dgftest
at
11:40 PM
1 comments
Labels: CMS, SharePoint, Web 2.0
Saturday, May 19, 2007
File Replicating / Synchronization - RedDot CMS Users | Google Groups
File Replicating / Synchronization - RedDot CMS Users | Google Groups
From the Google group for RedDot CMS Users (seems like a very practical suggestion from an excellent source :-)
"CMS publishing is the single most intensive process relating to
pretty much all aspect of the system, processor speed, disk speed and
network speeds are all heavily used. The thing to remember when
dealing with publishing is that, while you may only be setting up one
publishing job, if you are publishing to muliple servers, the job is
repeated each time for each server.
If you have multiple web servers and are using a load balancer, I
generally recommend that you set the CMS server up to publish to a
staging machine (an older, phased peice of hardware that is just
sitting around since so many company's seem to have them lately, and
then do exactly what everyone else has said and use something that
will monitor the folder and push the staging publish out to the web
servers, Cute FTP pro works really well for this and is only $69.00
(usd)
This actually serves two purposes. First, it cuts the publication time
down so that only one publishing job is involved and secondly, it
ensures uniformity throughout your live web servers.
I am currently running some benchmark tests relative to publishing and
should have that information in the next week or so.
Andrew Salik, Project Manager
RedDot Solutions, NA"
Posted by
dgftest
at
10:52 PM
0
comments
Labels: CMS, Infrastructure, RedDot
Thursday, May 3, 2007
CMS Watch finds MOSS 2007 ill-suited to Web Content Management -- CMS Watch
CMS Watch finds MOSS 2007 ill-suited to Web Content Management -- CMS Watch: " * For public-facing websites, the product lists for USD 41,000 per server, making it one of the most expensive licenses in its mid-market class.
* On the plus side, MOSS 2007 can be heavily customized and extended using traditional .NET approaches.
'MOSS 2007 might make sense for certain document-heavy Intranets,' Byrne added, 'but prospective customers should not assume that its ease of deployment for simple file sharing will equate to ease of implementation for managing complex web publishing operations -- for Web Content Management, MOSS is really more of a development platform.'"
Posted by
dgftest
at
11:13 PM
0
comments
