An OpenOffice based Content Management System?

bergeron76 asks: "Does anyone know of any OpenOffice based Content Management applications for Unix? I generate a tremendous amount of documents, spreadsheets, etc. and I'd like a way to organize them in a format other than a filesystem. A while back, I used a system called Docs Open. It was basically just a 'File Save [As]' dialog replacement database front-end for saving my document. I was _required_ to enter only meta-data(not the filename) about the document (keywords, description, etc) in order to save it. Conversely, it had a corresponding open-file dialog box that displayed the recent documents (DB records) and a query window for searching. It was a very nice system, and I'm wondering if anything like this exists for open-office or other popular non-Microsoft Office suites. I'm not seeking web-based systems, I'm seeking an integrated OO Plug-in or similar technology."

Comments

Take a look at Plone+CMFOODocument

[CRaMM]

http://plone.org

The CMFOODocument Plone product (http://www.icoya.de/support/download_area/zope/CM FOODocument) has some interesting bridging functionality.

I guess that when one uploads a OO Write document to a Plone site and it is converted to HTML by this product the content is added to the site catalog so it can be located on a seach by keywords.

Yo can try it at the Plone demo site http://demo.plone.org

I haven't' tried it myself though.

-

R

How about CVS or Subversion?

[hey!]

If you don't have a distribution and review process to be automated, maybe what you really want is a source code control system. You can use this to get every prior version and to tag related collections of documents and retrieve them in a single step. You'll have to teach cvs that oo's files are binary, but it should work fine.

Our windows developers are using a nice plug-in called Tortoise that patches explorer to integrate cvs with file browsing. You can update/commit, get change graphs simply by clicking on the file. Tortoise doesn't do anything that cvs doesn't do, but its a lot more easy and intuitive. We also use it for our documentation.

Of course, being able to use CVS like a file system, the way many IDEs do, would be even better. What would really rock is a plug in that stores the individual components of the OO file (content, stylesheet etc.) separately in a cvs archive. You could then get differences between different versions of a document.

Re:How about CVS or Subversion?

[AdamInParadise]

Now here is something amazing: OO files are just zipped archives of XML files. One could simply unzip the files, store the individual files in CVS and voila! the perfect revision management system. Well maybe not perfect, but probably much better than the Word one, especially with a better SCM than CVS and a little frontend to manages the fact that several files represent a single document.

Now, it seems simple, but last time I looked at the OO site, I didn't found anything like this. My guess at the time was that the built-in revision system was good enough.

Regards,