Hi, I am trying to evaluate some document management solutions based on these requirements. The problem is that many of these tools are full-fledged ECM solutions. I think Drupal is one of them.
Is there a way to use Drupal as a simple document management system based on these requirements ? I will try Drupal if that is what is recommended but any opinions or comments will also help.
Thanks, Mohan
Requirements :
We have a systems that receives and generates files and reports with financial data. These files could reside in the disk or they could be generated by the system. In the case of files in the disk we need to specify archival policies that the tool will use to move the files to its repository. We want to archive the reports generated on-the-fly by the system by invoking the webservice API of the tool.
We want to associate custom and standard annotations and metadata with these documents using the tools’ thick or think client or the WebService API. We also want to retrive and search these documents using the thick or think client or the WebService API. Document history is also required.
We want to view these documents in the browser. Some of these documents could be encrypted on the disk and they have to be decrypted before viewing. Volume labels should be associated with these document repositories so that the clients or the API know how to retrieve them and also support multi-tenancy.
As much as I love Drupal, you may want to look into Alfresco for this functionality. Drupal -> Alfresco integration does exist if you need it (http://drupal.org/project/cmis).
On Aug 19, 2011, at 12:20 AM, Mohan Radhakrishnan wrote:
Hi, I am trying to evaluate some document management solutions based on these requirements. The problem is that many of these tools are full-fledged ECM solutions. I think Drupal is one of them.
Is there a way to use Drupal as a simple document management system based on these requirements ? I will try Drupal if that is what is recommended but any opinions or comments will also help.
Thanks, Mohan
Requirements :
We have a systems that receives and generates files and reports with financial data. These files could reside in the disk or they could be generated by the system. In the case of files in the disk we need to specify archival policies that the tool will use to move the files to its repository. We want to archive the reports generated on-the-fly by the system by invoking the webservice API of the tool.
We want to associate custom and standard annotations and metadata with these documents using the tools’ thick or think client or the WebService API. We also want to retrive and search these documents using the thick or think client or the WebService API. Document history is also required.
We want to view these documents in the browser. Some of these documents could be encrypted on the disk and they have to be decrypted before viewing. Volume labels should be associated with these document repositories so that the clients or the API know how to retrieve them and also support multi-tenancy. -- [ Drupal support list | http://lists.drupal.org/ ]
-
Mohan Radhakrishnan -
Stephen Karsch