Hey,
On May 18, 2005, at 6:43 PM, Martijn Faassen wrote:
> We at Infrae had a brainstorming session today taking the concept
> map and seeing what was missing, and what we might want to change.
> Since I couldn't find an open source tool to edit .cmap files yet
> (hints anyone?), I'll just the result in a mail.
> What we would like to change
> -----------------------------
>
> There is a concept called 'DocumentStore' and 'DocumentRepository'.
> This begged the question where non-document media assets and so on
> are stored in this case. We would suggest changing these names to
> 'ContentStore' and 'ContentRepository' instead, and have a separate
> concept 'Document' and 'Media' (such as images and so on).
Well, the name of DocumentStore can change.
But I don't understand why you think a media is not a document ?
My definition of a document is some content + some metadatas.
You can have a .doc file + some metadata, an image + metadatas or
plain text + metadata.
In which way do you think that a media object is not a document ?
I think that a document management system has to deal with 2 kind of
data
- documents (content + metadatas)
- directories / vocabularies (list for metadata, users /
members / person directory, groups, etc.).
What do you think ?
> Concepts we thought of
> ----------------------
>
> Some of these might be implemented in ECM, some in the core Zope 3,
> some somewhere else entirely; we'll see and it's not very important
> right now.
+1 :-)
> Document - this could range from binary assets such as PDFs or Word
> Documents to HTML texts or fine-grained XML documents, so perhaps
> this needs subcategories. Some images would also be documents.
>
> XML-based content - fine-grained XML documents, or at least
> documents that can present themselves as XML. These could be schema-
> validated, have specific editing tools, could be XSLT transformed,
> XPath-based search, etc.
>
> Media - images, movies, sounds, that might become part of documents.
>
> Interactive media - such as flash and so on, perhaps even bundles
> of dynamic HTML content.
For me those 4 kind of content are all documents.
Different document types but all documents :-)
> Content Production/Editing tools - creation, editing, editors, WYSIWYG
The concept map is focused on the ECM Platform, that is to say the
core framework.
Content editors are very important but I think they deserve a new
concept map :-)
> Spell checking - useful to have while doing content creation
Related to Content editor. :-)
> Composite documents - Documents composed out of sub-documents and
> (media) assets.
Yes, that is very important. Florent has some though on that. He
should explain them here.
For me, Compound Document are severals document with relations to
bind them.
> Audit Trail - built using logging and such, tracking who did what
> when where.
yes. In the concept map it's called Logging Service.
This service have to provide :
- data for action auditing (ex: who suppressed this document)
- data for reporting (ex: how many document have been created in
this workspace since 2 month)
> Application-level Undo Facility - Zope has had undo for ages, but
> this undo sucks for application level undo. There are patterns to
> use to implement an application level undo.
I'm not sure this is a good feature : It's too low level. I prefer
versioning (automatic versioning for example) to allow users to go
back in history :-)
Undo in Zope is at the database level, I believe it's dangerous to
allow plain users make this kind of thing.
Moreover, if we use Events a lot, it will be difficult to undo all
consequences of an action on a document (for example, when DocA is in
state "approved", DocB go to "archived" and DocC is triggered to "to
update" because DocB is in archived. Undo can bread this kind of
chain integrity).
> Search - as opposed to indexing; good search builds on indexing but
> is more than that, such as search result presentation.
Related to User Interface. If the index engine is powerful, you can
build a fancy search interface. :-)
So it's not covered in this concept map (I think that the search UI
also deserve its own concept map :-).
> Link Management/Reference management - the can of worms where you
> don't want broken external and internal links on your site, and
> ideally have links be auto-updated when content moves, etc. This is
> a huge topic with many complications.
You are right. I think it's related to Relation management. Maybe we
can extend the concept map from the relation service.
> Web client-side - advanced stuff is possible with Javascript, AJAX,
> and the like. AJAX support is needed if only to be buzzword compliant.
Related to UI.
> Security - whatever is needed to make people feel secure. This ties
> in to audit trail, but also support for encryption, etc.
Yes. But it's not entirely related to the core platform.
> Access methods - HTTP, DAV, FTP, but also more specific systems
> like JSR-170 content repository API support, OAI-PMH metadata
> harvesting support.
+DeltaV.
> Syndication: RSS/Atom, OAI-PMH metadata harvesting
yes.
Could you explain more about OAI-PMH metadata harvesting (and with
which tool it allows to integrate).
> Transformation service: transforming one piece of content into
> another. OpenOffice into HTML, XML into other XML, DocMa-like
> functionality, etc.
Definitely. It should be part of the concept map of core platform :-)
> Metadata: Dublin Core, other metdata sets, metadata import/export,
> etc.
I think it's schema related. Metadatas are just properties that you
manage from a common schema for example.
> Taxonomy: tagging, content categories, folksonomy
Yes but same as above. I think those things are search features + UI
+ schemas.
> Content delivery/staging: staging to other ECM/Zope 3 servers,
> content delivery to non-Zope systems.
Yes too definitely. Maybe it's more related to an open interface to
the Platform allowing to deliver content in different formats.
> Enterprise Application Integration: integration with other big
> enterprise applications, such as databases, ERP, and so on.
> Messaging systems.
> Reporting: site statistics, access patterns, etc.
Related to User Interface also (the core platform should have a
powerful logging service and security model).
> It's a grab bag of issues, some of which may be out of scope for
> the concept map, but someone with a concept map tool could have a
> nice time trying to fit them into the existing map. :)
Well, maybe you got it now ;-)
I will extend the concept map with some of those ideas. Maybe you can
start a "feature" concept map.
Thanks,
EB.
--
Éric Barroca, Tel: +33 6 21 74 77 64 (mobile).
Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps
Gestion de contenu web / portail collaboratif / groupware / open source!
www.nuxeo.com - www.cps-project.org - www.indesko.com
Hosting: Nuxeo: Zope service provider