I am getting ready to get started on a rather large and comprehensive CMS project.
The jist is that there will be sort of mother site with a certain set of features that can spawn these sub sites with their own other features.
As an oh-by-the-way we got a, 'we need a fully featured document management system with version control and workflow.'
So I am doing my research and here I am. We will be working with Drupal for both the mother and daughter sites and already have plans for a dedicated solr/lucene box.
I see that openkm supports CAS so I think we are probably good to go. I would prefer something PHP based, but it doesn't seem any of the php solutions are up to snuff with either features or activity that is going on here.
Things we will definitely need that I am hoping someone can comment on how much heavy lifting is going to be needed:
* Direct http access of files; preferably a consistent URL for a given file even after it is updated. [ie we can have just one link to a file and the file can keep being updated but the URL for the 'latest file' will never change
* Document creation via some sort of webservice (so someone can upload a file into drupal and we can send the file and metadata to openkm)
* External authentication for file creation/access
* Web service at workflow completion (ie; after a file has been approved; execute some arbitrary code or update some external resource)
General questions I have are:
* We are going to end up having multiple 'sites' running on a single box and will want effectively different sets of files available for each of the sites; potentially to the point of not having a single administrator with access to all of them; is this possible with a single openkm installation; and/or is it possible to have dozens of openkm installations running simultaneously?
* Are there any known integrations with Drupal?
Fwiw, we are trying to talk them out of some of their requested features; but if that doesn't fly it looks very likely that openkm will be what we turn to. Any code created on the drupal end to marry the two will be released as a module.
Thanks
Geoff
The jist is that there will be sort of mother site with a certain set of features that can spawn these sub sites with their own other features.
As an oh-by-the-way we got a, 'we need a fully featured document management system with version control and workflow.'
So I am doing my research and here I am. We will be working with Drupal for both the mother and daughter sites and already have plans for a dedicated solr/lucene box.
I see that openkm supports CAS so I think we are probably good to go. I would prefer something PHP based, but it doesn't seem any of the php solutions are up to snuff with either features or activity that is going on here.
Things we will definitely need that I am hoping someone can comment on how much heavy lifting is going to be needed:
* Direct http access of files; preferably a consistent URL for a given file even after it is updated. [ie we can have just one link to a file and the file can keep being updated but the URL for the 'latest file' will never change
* Document creation via some sort of webservice (so someone can upload a file into drupal and we can send the file and metadata to openkm)
* External authentication for file creation/access
* Web service at workflow completion (ie; after a file has been approved; execute some arbitrary code or update some external resource)
General questions I have are:
* We are going to end up having multiple 'sites' running on a single box and will want effectively different sets of files available for each of the sites; potentially to the point of not having a single administrator with access to all of them; is this possible with a single openkm installation; and/or is it possible to have dozens of openkm installations running simultaneously?
* Are there any known integrations with Drupal?
Fwiw, we are trying to talk them out of some of their requested features; but if that doesn't fly it looks very likely that openkm will be what we turn to. Any code created on the drupal end to marry the two will be released as a module.
Thanks
Geoff