Content
Texte - Image
Texte
Here is a summary of the operations for creating a KRR and a KDM:
- Worksite Gallery, possibly within a collection1 (type Collection) to group the Worksites:
- A Worksite object, conventionally contextualized in a Worksite Collection for a given project.
- Briquette objects (recommended but not mandatory, read further), contextualized in the previous Worksite (in the Context Collection field), or elsewhere if they need to be reusable. This is not mandatory, it's just for classification.
- At least one Briquette or another ePLANETe object for each axis value. There are at least 4. These are all Crosslink Types to be used for Crosslinks to function:
- Axis Knowledge Holder
- Axis Conceptual Frame
- Axis Typology of Object to be Compared
- Axis Quality or Performance Issue
- KIK Gallery:
- A KIK object, conventionally contextualized in a KIK Collection for a given project.
- At least one IPR object or any ePLANETe object, contextualized in the previous KIK (in the Context Collection field). This is mandatory.
- If it's an object other than IPR, already existing elsewhere, simply add a new Context to it to contextualize it in the KIK.
- A Crosslink with the Worksite to use the KIK in a KRR.
- KRR Gallery:
- A KRR object, conventionally contextualized in a KRR Collection for a given project.
- At least one Crosslink with a Briquette or another ePLANETe object from each of the 4 axes (see above).
- KDM Gallery:
- A KDM object, conventionally contextualized in a KDM or Evaluation Collection for a given project.
- A "KDM Evaluation" type Crosslink with a KRR.
- At least one Stakeholder type Crosslink with a Briquette or any ePLANETe object.
Note 1
Project Collections for each Gallery mobilized in the project are normally already present. They are created by the "New Portal" form(still under development). They must be used as Entry Points for each object. This object can be a type of collection itself(like a KIK), a composite object(like a KRR or KDM), or an elementary object.
Note 2
Areas/Zones are used for classification clarity, not for functionality.
Source