SCIENTIFIC-LINUX-USERS Archives

April 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Francesco M. Taurino" <[log in to unmask]>
Reply To:
Francesco M. Taurino
Date:
Tue, 23 Apr 2013 08:37:49 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
try alfresco on premise. you can start with the community version and
then (pay and...) add some additional components to achieve compliance
level your customer require. It requires a java container like tomcat,
so you can give it a try even on windows platform, and is fully cmis
capable. you can access the document and record repositories via a
custom web interface, cmis browsers (libreoffice...), webdav or
integrated ftp or smb servers.

Francesco


Il 23/04/2013 06:17, Yasha Karant ha scritto:
> I apologize for posting this item to the SL list, but I need
> professional information that I have not been able to find from unbiased
> (not vendor) sources.
>
> My institution seems to be dedicated to the use of  applications for
> institutional management purposes (not research) from proprietary
> for-profit vendors (often licensed for high fees), particularly
> applications that only can be installed and run under a Microsoft
> environment. In most cases to date, we have been able to require
> compliance with ISO, IETF, W3C, and similar open standards to allow at
> least interfacing with open systems environments (such as SL).
>
> At present, there is a demand to move to a document management system,
> and a prime candidate appears to be Hyland OnBase.  I have found:
>
> The OnBase software has been designed to run within a Microsoft Windows
> environment
> (http://www.hyland.com/en/product/deploying-onbase/on-premises.aspx) but
> have not been able to find details on two issues:
>
> 1. Real (not vendor advertised) compatibility with open systems, at
> least from the client applications, including any MacOS X clients;
>
> 2. Security compromises and issues, vital because it is likely that
> there will be direction that confidential personnel records will be
> moved to this system.
>
> Off list, any information or references will be appreciated.  Again, my
> apologies for this posting.
>
> Yasha Karant

ATOM RSS1 RSS2