Document Management System mailing list archives

dms@odoo-community.org

Avatar

Re: [6071] Knowledge Management

by
InitOS GmbH, Frederik Kramer
- 03/04/2017 18:27:37
Am Montag, den 03.04.2017, 15:38 +0000 schrieb Johan Van Hirtum:
> Dear Frederik,
> 

Dear Johan

>  
>  
> Sounds very interesting ! Indeed is the lack of a good knowledge
> management a big disadvantage for Odoo.
> So I’m surely interested in your work.

Good to know. I'll keep you posted then

> We have stopped our development on Owncloud, because it’s limitation
> and moved to Alfresco. 

Well alfresco comes with a massive Java Stack (and of course powerful
Workflow management) this is why most of the companies we were
investigating used either classical file servers or OwnCloud.

> There are also more people in the Odoo community working on Alfresco.

Yes, i know.

> I think, maybe for SME, most of the functionality needed, could be
> build in Odoo itself, without connection to 3-partie software. 

Sure but that would require to rebuild a lot of things that are already
there to some extend and incarnated to the working processes of many
SME. Our approach is rather to provide best practise examples
connecting knowledge containers (such as Alfresco / OwnCloud) and just
exchange knowledge meta data (we've been creating an extra meta model
for that purpose)

> The Odoo document store is not that bad. And search algoritmes, file
> handling, protocol handling ( CIFS, WEBDAV, FTP,… ) is probably not
> that hard to build in when you have the knowledge -). 

Sure we use most of that technologies in our projects as well.

> There are standard libraries for most thing that could be a good
> start. Very important in knowledge management is security and user
> management / rights, and it is much easier to have that in 1 place. 

To be honest, i doubt that a bit. Our research rather said that this is
a myth to some extend. Ease of use and accessibility of information is
much more important than having an enterprise grade security layer
(although we certainly develop that as well but not with the highest
priority)

> And it would be a good start to enhance the power of Odoo here… (
> encryption, different admin roles for developing and data ( you don’t
> want even your developer to see delicate accounting / HR data ), … ).

no sure, a certain level of role based security is important i do
definitely agree.

> But a connection with a specialist system is OK to of course.
> Important to me is that the integration is completely invisible for
> the user :
>                 - When you want to upload files, in Odoo the Alfresco
> client opens with the right target map opened. So you have all upload
> power of Alfresco ( Owncloud ).

Thats exactly how we want to build it.

>                 - When you want to view a file in Odoo, the file is
> opened in or the Alfresco client or as a link via Webdav, so you can
> edit the file on your windows computer directly.

bahhh Windows ;-) No you are right that feature is also necessary.

>                 - Properties / rights / encryption is synchronized.

Full sync here requires a lot of work and abstraction. I think we gonna
build a first running / working prototype with some exemplary systems
here.

> When SME users must be concerned about the system in the backend or
> must do the storage 2x or the storage structure differs in the
> different systems, after 2 months you have a complete mess and no one
> is using the system any more. 

Thats exactly what we do want to avoid !

> The knowledge management must be very simple to use. 

That is an overarching requirement we found in our interviews as well
as the extant literature we've been analysing. I totally agree

> Extra work is, surely in modern business where there is no time left,
> to be avoided.

Absolutely.

> I try to find the time to look to the documents in the link provided.
>  

Probably i am gonna rework the findings we've been obtaining in a more
executive style manner, somewhen in the weeks to come so you might
spent your time more wisely and wait to comment on those unless you are
very interested in the research methods and data source we've been
analysing.

> Much success with your great initiative !

Thanks a lot. I'll keep you and the community posted

Frederik
>  
> Van Hirtum Johan     
>  
> Van: Frederik Kramer [mailto:frederik.kramer@initos.com] 
> Verzonden: maandag 3 april 2017 15:09
> Aan: Contributors
> Onderwerp: [6071] Knowledge Management
>  
> Hello out there dear Odooers, 
>  
> as some of you might have heard during the Odoo Enterprise in 2016
> initOS together with the University of Leipzig and the company
> AgriCon
> has been funded by the German Ministry of Education and Research to
> develop a knowledge management system for SME. No surprise initOS is
> going to use Odoo for that purpose ;-). 
>  
> Since the beginning of the year we are pretty much done with the
> founding qualitativ research. We know by now that what is / has been
> developed under the umbrella of knowledge management app in the
> current
> OCA repository (as well as all market relevant tools for SME-based
> KM)
> is quite limited to document management (and wiki functions for the
> poprietary tools). 
>  
> However, knowledge management is way more than this:
>  
> 1.) Knowledge resides explicitly in various expressions (e.g.
> documents, models (e.g. bpmn processes), architectural blueprints,
> presentations, wikis, ticket systems, e-mail, chat and voice
> protocolls, videos) and as parts of the business entities in ERP
> systems (models in Odoo's nomenclature).
>  
> 2.) To a large extend knowledge still and will continue to reside in
> the brains of the employees (who knows what in which context) -> also
> known as tacit knowledge
>  
> 3.) Knowledge is usually context specific (i.e. knowlegde in action =
> information).
>  
> 4.) For SME in todays global and dynamic markets in becomes more and
> more relevant to have access to all "silos" of relevant explicit
> knowledge and being able to link them to their business processes.
>  
> 5.) Last but not least SME need a management method that allows
> owners
> as well as knowledge workers to set targets, measure achievements and
> earn reputation in the knowledge management (i.e. identifying,
> sharing,
> storing, using, improving, combining) "game"
>  
> Having that high level goals in mind we are now searching for the
> right
> place to put our work initiative that will contain a gradually
> growing
> number of code pieces that will be trying to solve some of the
> aforementioned requirements.  
>  
> Whereas i personally feel the OCA knowledge repository might be an
> appropriate place for it, i am not sure at what point it makes sense
> to
> start pushing our research artifacts to the community and whether it
> makes really sense to put under the existing OCA knowledge repository
> or start a new repository "knowledge management system" with that
> special focus.
>  
> Hence, i kindly ask especially the historic contributors and Odooers
> with interest in knowledge management to share their thoughts and
> ideas. While the research has a focus on applicability for single
> demonstrative cases (Agricon in our case) the whole MACKMA team would
> love to take also your ideas into account (i.e. on our product
> backlog)
> in order make as much as we can out of our public funding.
>  
> We would also love to join forces with customer projects that have
> special requirements with regard to KM in order not to develop the
> wheel twice. 
>  
> For those particularly interested in the research let me kindly point
> out the list of research publications two of which have been
> presented
> at highly ranked international research conferences in the USA last
> and
> beginning of this year (if somebody is interested in reading it and
> has
> now access to the AMCIS paper, just let me know, the HICSS one is
> open
> access)
>  
> http://www.mackma-project.eu/publikationen/
>  
> I would really appreciate to get as much as possible feedback /
> advices
> on the matter. As soon as we have the first presentable piece of work
> ready i would be eager to share a presentation as well our backlog
> with
> interested people from the community. Just to inform you
>  
> For know we started to work on
>  
> a) an implementation of our "knowlede artifact" concept that will
> stand
> as a meta model extension for each piece of explicit knowlegde
> (inside
> and external to Odoo)
>  
> b) a connector that allows us to prototypically connect OwnCloud and
> Odoo using a)
>  
> c) research of a message broker to built an abstraction layer between
> Odoo and external knowledge systems (e.g. DocuWiki, OwnCloud,
> Redmine)
>  
> Looking forward to receiving feedback, ideas and the like
>  
> Frederik
> -- 
> Dr.-Ing. Frederik Kramer
> Geschäftsführer
>         
> initOS GmbH
> An der Eisenbahn 1
> 21224 Rosengarten
>         
> Phone:  +49 4105 56156-12
> Fax:    +49 4105 56156-10
> Mobil:  +49 179 3901819
>         
> Email: frederik.kramer@initos.com
> Web:   www.initos.com
>         
> Geschäftsführung:
> Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
>  
> Sitz der Gesellschaft: Rosengarten – Klecken
> Amtsgericht Tostedt, HRB 205226
> Steuer-Nr: 15/200/53247
> USt-IdNr.: DE815580155
>  
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/document-management-s
> ystem-31
> Post to: mailto:dms@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

Reference