Re: Re: [OSCOM] Open source CMS / documents are content/

Hi Paola  

I think I should be clear in what exactly I am looking for..
I am planning to develop a system which manages a document life cycle..
i.e. from the creation of the doc till archival ..

This is how the sys should work..
The end user creates a document say MSWord or a pdf in his fav editor.and then logs on to my system initates a work flow by uploading the document, now based on the workflow defined the doc should be routed to another user who is responsible for reviewing the content and then to DTP editor who formats the doc and then to super user who approves that..after the doc gets aprroved it should be converted to a defined format say a pdf and then it gets distributed thru various channels ..

so, the system should have the following components such as..
1. A Document repository with features like
versioning
Access Control
and also it should be JCR(JSR 170) compatible
etc..
2. A Document mgmt server with provides
BPM (Workflow)
Managing user Access (roles and permissions)
Rendition
Auto tagging
indexing
catogarization 
Search
Archiving (it can be scheduled job which archives docs which are n days older)
3. A Distribution Engine which supports various channels of distribution like smtp, ftp etc...

what I don't need is an authoring environment, i.e. is WYSIWYG editor for editing my content..

so I think its better to look for some DMS rather than CMS...

Mohan
  


On Fri, 18 Mar 2005 Content-wire Research wrote :
>
>Hay Oliver
>
>
>Both types of system  generally support:  versioning of objects, workflow tools, meta-data
>>management, roles and permissions, indexing and searching, hierarchical directory structures (and other tools to organize objects).
>
>
>what about  browser based?
>With SOA  to become dominant environment in the future, can the home based/remote user  expect
>a tool that support file handling via browser/IP?  Is this a common feature in typical DMS, in you experience?
>I know there are some tools that support it, by I dont think it has been the norm historically
>
>>
>>To enhance a good content management system to do document management, one would need to add support for mass importing and indexing large collections of documents
>
>re: mass import
>In my experience 'import' functions are not limited by size, ie the volume of files is irrelevant to the system design (other than hardware and cache size perhaps) the function is simply  'select file to be imported'  and 'import files' - two clicks - please correct me where I am wrong
>
>re: indexing
>wouldnt the same indexing that supports search and retrieval - generally built in in advanced systems - be
>used for this purpose, If necessary maybe duplicated and  with certain variable and parameters configured ad hoc?
>
>
>an OCR tool to index scanned content,
>
>I believe they are rather standard add ons, even available free (not sure how good)
>
>and a UI  for internal users that emphasizes adding and versioning documents, and
>>organizing and searching the library.
>
>
>I think the benefits of your suggested functional CMS extension could outweigh the cost of buidling a straight DMS, although the amount of thinking around it would have to be marginally more intensive,
>allowing of course for some situations when the option is not desired/preferred for whatever reason
>
>Paola DM
>
>
>
>>
>
>
>_______________________________________________
>General mailing list
>[email protected]
>http://oscom.org/cgi-bin/mailman/listinfo/general

_______________________________________________
General mailing list
[email protected]
http://oscom.org/cgi-bin/mailman/listinfo/general