diff --git a/models/Dementia-Treatment-Concepts_PR (3).json b/models/Dementia-Treatment-Concepts_PR (3).json
new file mode 100644
index 0000000..5343697
--- /dev/null
+++ b/models/Dementia-Treatment-Concepts_PR (3).json
@@ -0,0 +1,21937 @@
+{
+ "phData": {
+ "metis": {
+ "name": "Dementia-Treatment-Concepts",
+ "description": "New Project to start modelling",
+ "allowGenerateCurrentMetamodel": false,
+ "metamodels": [
+ {
+ "id": "32b03aab-bd61-4924-4d6c-ce36e4537774",
+ "name": "AKM-IRTV_MM",
+ "description": "",
+ "metamodelRefs": [],
+ "subMetamodelRefs": [],
+ "subModelRefs": [
+ "04bf44ba-8def-4427-063d-14119c8e6b1b"
+ ],
+ "subMetamodels": [],
+ "subModels": [
+ {
+ "id": "04bf44ba-8def-4427-063d-14119c8e6b1b",
+ "name": "Build a Concept Model",
+ "description": "### Concept Model (TD) Model\n\nAs a way to Explore and Understand the problem space. we will create a Product-(Information and Concepts) and Functional-model (Tasks and Roles)\n\n##### Example Model\n\n \nClick on the picture to open in New Tab!\n\nAs you see there are also additional ObjectTypes that can be added to the TD-model here.\n\nVi use the IRTV_MM Types to build this model.\n\n##### IRTV_MM Metamodel\n\n \nClick on the picture to open in New Tab!\n\nThe main Objecttypes in IRTV is Information Role, Task and View EntityTypes.\n\nThese are the types that will be generated to Object types in the resulting Metamodel.\n\nIn addition we have the proposedType Property added to the IRTV EntityTypes.\n\nThe MetaModel Object is used to point to which EntityTypes are included in the metamodel, in this cas IRTV EntityTypes\n\nYou can find more info following this link : \n A Demo Solution Model...\n\n",
+ "sourceMetamodelRef": "",
+ "targetMetamodelRef": "",
+ "sourceModelRef": "",
+ "targetModelRef": "",
+ "includeSystemtypes": true,
+ "includeRelshipkind": false,
+ "isTemplate": false,
+ "templates": [],
+ "objects": [
+ {
+ "id": "e251958b-5946-40e9-a50d-98354faaca15",
+ "name": "Create initial Containers",
+ "description": "",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "6d2249aa-d9e2-4f31-1dc9-70a5e4a4b457",
+ "name": "Test",
+ "description": "\n Build the Concept model for the Metamodel
\n\n ## Build the metamodel\n\n Let us start with the built-in metamodel:\n\n \n\n The left pane contains the object types in the initial metamodel, that the user can use to build a type definition model.\n\n \n\n\n Model the type definitions
\n\n ### Model the type definitions\n\n ",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "6fbfa4bc-c6c2-4706-ffd1-06ab413a24f1",
+ "name": "Create Concept (Information)",
+ "description": "From the Palette (left pane) drag the **Information** and drop it into the Container **Types**. Give the object a **name**.\nRight-Click the object to edit description and **proposedType**.\n\nThe attribute \"proposedType\" is used to give the Concept-/ Information-object a proposed TypeName.\nThe TypeName will replace the Typename of this object.\n\n \nClick on the picture to open in New Tab!",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "5dad7468-921b-44d5-97dc-ab8217830369",
+ "name": "Create Relationship between Concepts",
+ "description": "Connect two EntityType objects. \n\n -Point the cursor to the edge of the object (a curved arrow appears). Click and hold while dragging over and drop on an other object. Select Relationship type **relationshipType**.\n\n -Then edit the relationship name to give it a name.",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "b59ce2f1-a6a6-4337-e047-a51e753634c2",
+ "name": "Create Tasks working on the Information",
+ "description": "From the Palette (left pane) drag **Role** Type and drop it into the \"Task container\". Give the task a name (should contain a verb) and description.\n\nDrag the relationship **worksOn** from **Task** to **EntityType.**\n\n \nClick on the picture to open in New Tab!",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "e6b8a50e-ce49-44f1-a5a8-e93772892c22",
+ "name": "Create performing Roles",
+ "description": "From the Palette (left pane) drag **Role** Type and drop it into the \"Role/Task container\". Give the task a name and description.\n\n(Role here is more a \"process role\" than an \"organisational role\"\nIts normally not a Position)\n \n\nDrag the relationship **worksOn** from **Task** to **EntityType.**\n\nMore about Role
\n\n(from ChatGPT)\n\nIn general, an organizational role refers to a specific position or job within an organization, while a process role refers to a specific role or responsibility within a business process.\n\nAn organizational role is typically defined by the organization's structure and hierarchy, and is often associated with specific responsibilities, authority, and accountability. Examples of organizational roles include manager, director, and team lead.\n\nA process role, on the other hand, is typically defined by the specific business process being executed, and is often associated with specific tasks, activities, and decision-making responsibilities. Examples of process roles include approver, reviewer, and executor.\n\nIn summary, while both organizational roles and process roles are important in defining the structure and responsibilities within an organization, they differ in terms of their scope and focus.\n \nClick on the picture to open in New Tab!\n\nAs you see there are also additional ObjectTypes that can be added to the TD-model here.\n\nVi use the IRTV_MM Types to build this model.\n\n##### IRTV_MM Metamodel\n\n \nClick on the picture to open in New Tab!\n\nThe main Objecttypes in IRTV is Information Role, Task and View EntityTypes.\n\nThese are the types that will be generated to Object types in the resulting Metamodel.\n\nIn addition we have the proposedType Property added to the IRTV EntityTypes.\n\nThe MetaModel Object is used to point to which EntityTypes are included in the metamodel, in this cas IRTV EntityTypes\n\nYou can find more info following this link : \n A Demo Solution Model...\n\n",
+ "sourceMetamodelRef": "",
+ "targetMetamodelRef": "",
+ "sourceModelRef": "",
+ "targetModelRef": "",
+ "includeSystemtypes": true,
+ "includeRelshipkind": false,
+ "isTemplate": false,
+ "templates": [],
+ "objects": [
+ {
+ "id": "e251958b-5946-40e9-a50d-98354faaca15",
+ "name": "Create initial Containers",
+ "description": "",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "6d2249aa-d9e2-4f31-1dc9-70a5e4a4b457",
+ "name": "Test",
+ "description": "\n Build the Concept model for the Metamodel
\n\n ## Build the metamodel\n\n Let us start with the built-in metamodel:\n\n \n\n The left pane contains the object types in the initial metamodel, that the user can use to build a type definition model.\n\n \n\n\n Model the type definitions
\n\n ### Model the type definitions\n\n ",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "6fbfa4bc-c6c2-4706-ffd1-06ab413a24f1",
+ "name": "Create Concept (Information)",
+ "description": "From the Palette (left pane) drag the **Information** and drop it into the Container **Types**. Give the object a **name**.\nRight-Click the object to edit description and **proposedType**.\n\nThe attribute \"proposedType\" is used to give the Concept-/ Information-object a proposed TypeName.\nThe TypeName will replace the Typename of this object.\n\n \nClick on the picture to open in New Tab!",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "5dad7468-921b-44d5-97dc-ab8217830369",
+ "name": "Create Relationship between Concepts",
+ "description": "Connect two EntityType objects. \n\n -Point the cursor to the edge of the object (a curved arrow appears). Click and hold while dragging over and drop on an other object. Select Relationship type **relationshipType**.\n\n -Then edit the relationship name to give it a name.",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "b59ce2f1-a6a6-4337-e047-a51e753634c2",
+ "name": "Create Tasks working on the Information",
+ "description": "From the Palette (left pane) drag **Role** Type and drop it into the \"Task container\". Give the task a name (should contain a verb) and description.\n\nDrag the relationship **worksOn** from **Task** to **EntityType.**\n\n \nClick on the picture to open in New Tab!",
+ "abstract": false,
+ "viewkind": "",
+ "typeRef": "3979fb2c-71e3-4054-745d-ee062b3689e5",
+ "typeName": "Task",
+ "typeDescription": "",
+ "propertyValues": [],
+ "ports": [],
+ "markedAsDeleted": false,
+ "generatedTypeId": "",
+ "modified": true,
+ "nameId": "Task",
+ "category": "Object",
+ "sourceUri": "",
+ "relshipkind": "Association",
+ "valueset": null,
+ "copiedFromId": "",
+ "proposedType": "",
+ "text": ""
+ },
+ {
+ "id": "e6b8a50e-ce49-44f1-a5a8-e93772892c22",
+ "name": "Create performing Roles",
+ "description": "From the Palette (left pane) drag **Role** Type and drop it into the \"Role/Task container\". Give the task a name and description.\n\n(Role here is more a \"process role\" than an \"organisational role\"\nIts normally not a Position)\n \n\nDrag the relationship **worksOn** from **Task** to **EntityType.**\n\nMore about Role
\n\n(from ChatGPT)\n\nIn general, an organizational role refers to a specific position or job within an organization, while a process role refers to a specific role or responsibility within a business process.\n\nAn organizational role is typically defined by the organization's structure and hierarchy, and is often associated with specific responsibilities, authority, and accountability. Examples of organizational roles include manager, director, and team lead.\n\nA process role, on the other hand, is typically defined by the specific business process being executed, and is often associated with specific tasks, activities, and decision-making responsibilities. Examples of process roles include approver, reviewer, and executor.\n\nIn summary, while both organizational roles and process roles are important in defining the structure and responsibilities within an organization, they differ in terms of their scope and focus.\n