Rating: +0
We all need these systems yet we hate the one that is currently in place...why? What would you do differently if you created such a system?
Happy Friday,
Kim
Kimberley,
More core functions need to be built into the OS Kernel, (hint hint Linux distros), for example how a document becomes part of a library collection hasn’t changed for ump-teen years, File, Save As, then some rudimentary VB script to save to Library X or Y, etc. The local executed VB script, or whatever, has always meant local software, making sure the right versions of 'whatever' are available locally, etc. Why isn't a function Document Management System function like file save as hooked into the OS Kernel? I should be able to do a File, Save and see the document repository libraries as part of the Windows Common Dialog just like an F: drive.
DRM Policies as well as encryption should be managed by the DM system and should be built into portable "documents" policies should be declared as both global and explicit.
Features like redaction should be universal and work based on the same DRM standards that are used for iPod tunes. That's just a start.
Core file system features, read, write, create, migrate all should be moved up the stack and into the OS Kernel.
Secondary features should exist as web services so a community of developers can make key features widely accessible.
Reduce the foot-print for deployments of large scale systems, by scaling back the database requirements.
There is so much more that can be done, but that’s a start.
Good Luck,
Peter
August 2008