Re: Sharepoint vs. Livelink



On May 9, 2:04 pm, mgauf <mg...@xxxxxxxxx> wrote:
I am in the process of researching a new document storage technology
for a client's policies and procedures. Both Sharepoint and Livelink
have been raised as options.

What I am looking for is a robust & expandable document storage/
retrival system that will accommodate both a menu-based navigation as
well as an advanced search engine mechanism.

The clients want top be able to upload, policies, procedures, work
instruct., and process flows so that they can be shared thru the
Intranet. The ability to thoroughly tag/mark the documents to ensure
the best possible search results is also a key. At this time, the
documents will be uploaded in pdf form.

Also, some of the admin. section must be user friendly in order to
deal with differing user levels of techno-knowledge, particularly if
more than 1 person will have upload permission.

I have reviewed demos of both from their respective websites,
performed a web search for comparisons of the 2, and talked to people
who swear by both, but I have NOT been able to take a test drive for
myself.

I am looking for critical, honest assessments, particularly for the
aforementioned purpose.

Thanks Mike

Mike,

It all depends.

Is your customer a Windows shop? Do they have investments in .Net? Do
they have internal resources who know Microsoft technologies well? Do
they use IIS, MS-Office, and MS-SQL server? Are they aware that
Sharepoint needs programming just to get it to do anything useful in
Document Management?

Same with livelink... focus on what the total costs and efforts are in
getting it to work for your customer.

If they are not strong with development and may not have the budget to
hire contractors, I would suggest buying a system that is an EDMS to
start with - there are any number of them out there... Alfresco,
FileDirector, and many, many more. We found that smaller organizations
focused on EDMS tend to have better and more feature-rich products
than products from behemoths, just because the focus is on EDMS and
not on "having a complete does-everything platform for the Fortune
2000".

The idea is to make a functional non-technical feature set that the
customers are going to use tomorrow, in 3 months, and 6 months.
Anything longer that that, even the customer wouldn't know what
features they need. Then, take each product and check if the feature
is supported by that product. Then drill down to budget and
architecture, finally choose the one that meets IT approval the most.

Hopefully this helps.

You may not find a head-to-head comparision on any 2 competing DMS
products, but if you end up doing one, I would appreciate getting a
copy of it.

Regards,
Milind Joshi
IDEA TECHNOSOFT INC.
http://www.ideatechnosoft.com
.



Relevant Pages

  • Re: So long Raining Data. Hello TigerLogic Corporation.
    ... MARKET under that term is where the point was being made. ... only customer base, the only community from which my company currently ... We have to take that feature all the way from ...
    (comp.databases.pick)
  • Re: Edit In Datasheet Control
    ... of enhanced Sharepoint integration, which is why the customer are upgrading ... >> Office Professional Enterprise, however I cannot understand the reasoning ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Versioning,creating web pages in Word 2007
    ... combining document changes.Is it the option i use for comparing and merging ... I would like to know if i can insert movie clips using Sharepoint? ... The old File=>Versions feature is gone from Word 2007. ... I seem to understand that versioning and creating web pages can be ...
    (microsoft.public.word.docmanagement)
  • Re: With Agile methods, we are measuring the right things
    ... LOC metrics and feature value metrics are quite different. ... particular customer satisfied for a particular application. ... Without such measures developers may not ...
    (comp.object)
  • Re: COBOL and XML (was Re: OT - "lie" vs "error")
    ... WG4 directed not only that the capability but also the approach to providing ... why it was a TR and not "just" a feature for the next standard). ... The only way Unisys folk are going to be stimulated to explore whether it ... compilers to include this feature is from *customer* input. ...
    (comp.lang.cobol)