Forum OpenACS Q&A: New project CMS, KM etc.
We're early in the design phase of a new project for a large government body. We will probably be using the latest version of the OpenACS, Oracle 9i if possible. The main requirements are as follows, quite roughly.
1) Content management - version control, workflow, content approval, metadata storage, permissions, workflow.
2) Knowledge management - we're really trying advanced searching (complex searching including concepts etc. mostly hidden from the casual user), taxonomy of concepts / keywords, Browse type search involving the taxonomy or part of, user "categories of interest", some kind of "push" of relevant documents to users, experts database - "who knows what" , Find "content like this", My bookmarks / share bookmarks, link content / share links.
3) Multilingualisation - fairly standard "label multilingualisation " content in one language at a time.
4) Workflow - Not strictly content related.
5) General collaboration: FAQ, bboard, file storage.
6) Portal type easily customizable interface with news and other feeds for "stickiness". Some kind of access to e-mail here also would be desirable.
Off the top of my head I imagine we'll be trying to get the Openacs 4.6.1 working with Oracle 9i, and all the obvious packages. Where I see us extending the toolkit would be in the areas of:
a) Advanced searching - not sure what to do yet exactly but looking into it.
b) Taxonomy - Try to leverage functionality from the following features in Oracle text: Knowledge base - make visible and extendable to the user by using their browser, use some of it for interest categories etc, Section group, Thesaurus, Lexer, Relevance ranking.
c) Look at interoparabilty between Oracle 9i and openacs - Portals, single sign on / LDAP etc.
d) Portal - we may want to add some functionality here.
e) Experts database.
f) "Push" - a bit like "new stuff".
Anyway most of this is just thinking out loud and it's very early days. I will keep you posted if you're interested and I'd be grateful for any comments or if you just want to watch this space...
Categorization ... there's some categorization stuff available already in the content repository and there's work underway do do a more general categorization package, check the recent thread in regard to this. Folks should organize and work together if possible, though I realize client deadlines can make this hard or impossible to do. There's no reason to duplicate effort if we can avoid it, and general categorization is badly needed.
Also if you're not already familiar with the templating system's form builder package, study it and the ad_form wrapper function we now use to write self-submit form generation and handling scripts. Makes things much simpler. The autogenerated forms mentioned above also uses the templating system's form builder package so you can customize the look of input forms site-wide by writing one new template file.
Workflow - we have a new, simplified workflow package courtesy of Lars Pind, who wrote the original acs-workflow while at Ars Digita. The new one uses a finite-state machine model rather than petri nets - FSMs are sufficient for the simple workflow requirements we've run into and relatively few people are familiar with Petri nets.
I think it might be nice if the client has a choice of how the content lays out. You mentioned a portal-like layout potential. I think a good content management system would allow an authorised user to associate the inital content to several other types of content.
For example a news item might have three pictures, or none. It might be linked to other news stories. It might be linked to a critical document that has just been published.
A news story with three pictures, just for example, would imply that instead of just designing one portal like template, you would design a more flexible system that could respond to the type of content.
Don and Lars can tell you about the best functional way to do these things. I've just had alot of experience with what clients want. Our people want alot of flexibility with the design, but thats because we are an extremely reactive bunch, used to changing our entire homepages daily. You might find that being in a Goverment situation, you'll need to change the front pages less often, but you'll get alot less minor hassle if you allow for more flexibility.
I hope this helps - it might seem a bit obvious :)
I'm planning to dive into cleaning up our portals stuff relatively soon, that's my plan at least ...
Yes, it should be done in a Portal-based form, that's the way to go.
Are you planning to discuss openly with the community about the Content management & Knowledge management?
Both a really important issues for the future of openacs, I strongly suggest that the core things should be widely discussed here.
May I ask you how your project is progressing? We are currently setting up a KM group at La Salle university in Barcelona, and a mulilingual search engine would also be one of our first goals.
However, the second goal would be a "personalized" search engine, using Bayesian networks for selection purposes and a lot of other modules.