Services management

Introduction

This schema represents the architecture of the services management feature.

Schema

Description

ServiceHold information about the service
[…]_idprimary key of the service
[…]_labellabel of the service
ServiceProperyHold the additionnal field added to an entity by a service
[…]_service_idservice key
[…]_keyproperty key
[…]_defaultdefault value of property(needed?)
[…]_typetype of field added to the entity by this property
[…]_minmin number of values for this property by entity, NULL == 0
[…]_maxmax number of values for this property by entity, NULL == infiny
ServicePropertyXXXSpecialization of ServiceProperty. Property listed here can be linked to an XXX
[…]_id= serviceproperty_id
XXXServicePropertyValueValue of a property for an XXX
[…]_sericeproperty_idkey of the property
[…]_XXX_idkey of the XXX
[…]_valuevalue of the property
ServiceXXX
[…]_id
XXXServiceSpecialization of Service. Service listed here can be linked to an XXX
[…]_service_idkey of the service
[…]_XXX_idkey of XXX

MCD

The same model should be added for P_ tables  Service schema

Validate

  • Mehdi : Ok
  • Anthony : -
  • Pierre : what about putting serviceproperty specialization in serviceproperty directly ? ⇒ ex: 2 serviceproperty quota (one for user, one for mailshare). apart that mailshare is not handled by this.. might be too formal and resolving only a small part of the problem ? module code have to know the properties…
  • Thomas : works for me, service_key only (rm key label) (mehdi : Done)
specification/db/services.txt · Last modified: 2009/11/03 13:57 (external edit)
Driven by DokuWiki