Thank you for the information (again, off list is just fine) -- however, 
my institution only wants monopoly proprietary for-fee software (and 
proprietary hardware in so far as possible).  Thus, I am attempting to 
find out if Hyland OnBase is compatible with open systems clients and 
what are the known experiences with this application/service -- 
including known previous security issues or compromises.  Thanks again 
for any insight -- not vendor propaganda, however.

Off list responses are just fine.

Yasha Karant

On 04/22/2013 11:37 PM, Francesco M. Taurino wrote:
> 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