PLOG 2016

PLOG 2016
What is IMIO ?
1.
Working only for the public sector ;
2.
Offering Open Source applications as SaaS ;
3.
A few figures :
●
Customers :
70% walloon
municipalities
●
Deployed sites : ~150
●
Deployed plone applications : ~200
●
Deployed other applications : ~50
●
Managed physical servers : ~30
Applications
Applications :
●
Official meetings management (PloneMeeting)
●
Town planning process (Urban)
●
Mail management system (collective.dms.*)
●
Website, Services toward citizen (cpskin.*)
●
Project and process management (imio.project.*)
●
...
Official meetings management
This let's user manage their official meetings : college or council in a
town, but can be used with any kind of official meetings like schools,
private sector councils, ...
1. Dashboards : imio.dashboard using eea.facetednavigation, collective.eeafaceted.
collectionwidget, collective.eeafaceted.z3ctable, imio.actionspanel, collective.
compoundcriterion, collective.behavior.talcondition ;
2. Generation of desktop type documents (PDF, ODT, …) using collective.
documentgenerator ;
3. Preview of files (annexes) in the browser (collective.documentviewer) ;
4. Integration with other systems thru webservices (SOAP/WSDL) ;
5. ...
Official meetings management
Dashboards
1. Based on eea.facetednavigation;
2. Widget collective.eeafaceted.collectionwidget that displays a list of “base
searches” actually plone.app.collection Collections, faceted result is displayed in a
z3c.table using collective.eeafaceted.z3ctable ;
3. Complex catalog query management using collective.compoundcriterion ;
4. Widget displayed as a portlet and managed “TTW” using conditions to display a
search (collective.behavior.talcondition) ;
Collective.documentgenerator
1. Generation of desktop type documents (PDF, ODT, XLS, …) ;
2. It’s be used on Standard Plone or on Application like PloneMeeting, Urban, Mail
management system, …;
3. Using appy framework;
Mail management
This aims to be a document management system. For now, it focuses
essentially on incoming and outgoing mails.
Goals:
●
Reference received and sent mails
●
Manage mail distribution
●
Follow mail treatment
Mail management
Functionalities:
1.Scanned mails import (via webservice)
2.Mail content (collective.dms.*)
3.Document preview (collective.documentviewer)
4.Team and validation roles (dexterity.localrolesfield)
5.Sender and recipient management (collective.contact.*)
6.Dashboards (imio.dashboard: glue on eea.faceted, collective .eeafaceted.
collectionwidget, collective.eeafaceted.z3ctable, etc.);
7.Task management (collective.task) ;
8.Password policy (Products.PasswordStrength)
9.Informative messages (collective.messagesviewlet)
10....
Mail management
dexterity.localroles = automatic local role attribution by state
●
Same as DCWorkflow but
●
Plone UI configuration
●
Related objects local role attribution
●
Base for following product
dexterity.localrolesfield = same but principal is given in a field
●
Mono or multi-value z3c field, listing principals
●
Automatically displayed in ui configuration
●
Add suffix concept to work with collective.contact.plonegroup
collective.contact.plonegroup
●
Internal departments definition
●
Functions definition
●
Combination to create Plone groups like “org_function”
Website
Complete website solution :
●
Specific workflows making build of a navigation (portlet and menus) easy (cpskin.
workflow and cpskin.menu)
●
Management of subsites (cpskin.minisite)
●
Different kinds of responsive skins with « controlled customization » (cpskin.theme,
diazotheme.frameworks and cpskin.diazotheme.*)
●
Management of homepage with news, events and trends items (cpskin.slider)
●
Use some collective addons (imagecropping, facetednavigation, contentleadimage,
plonetruegallery, ckeditor, collective.contact.*, collective.geo.*, cookiecuttr,
PasswordStrength, …)
All our website are “Dockerized”