bump frontend

Temporarily rename the change-event-result organization relationship (#94 )
This relationship uses the same `org:organization` predicate that is also used for the local involvements relationship. When querying for local involvements data when an organization also has change events data, mu-cl-resources receives the change events data instead and runs into errors. This is likely a bug in the micro service itself. Renaming the predicate is a quick workaround so we have more time to find the real solution for the problem without a broken app.
2022-01-26 15:43:11 +01:00 · 2022-01-25 20:04:18 +01:00 · 2022-01-24 11:28:47 +01:00 · 2022-01-20 14:53:33 +01:00 · 2022-01-20 10:27:55 +01:00
6 changed files with 69 additions and 3 deletions
--- a/config/migrations/2022/20220125185900-rename-change-event-result-relationship-predicate.sparql
+++ b/config/migrations/2022/20220125185900-rename-change-event-result-relationship-predicate.sparql
@@ -0,0 +1,18 @@
+PREFIX ext: <http://mu.semte.ch/vocabularies/ext/>
+PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
+PREFIX org: <http://www.w3.org/ns/org#>
+
+DELETE {
+    GRAPH ?g {
+      ?changeEventResult org:organization ?organization .
+    }
+} INSERT {
+    GRAPH ?g {
+      ?changeEventResult ext:resultingOrganization ?organization .
+    }
+} WHERE {
+  GRAPH ?g {
+    ?changeEventResult a <http://lblod.data.gift/vocabularies/organisatie/VeranderingsgebeurtenisResultaat> ;
+            org:organization ?organization .
+  }
+}
--- a/config/migrations/20220120100418-remove-old-reasons.sparql
+++ b/config/migrations/20220120100418-remove-old-reasons.sparql
@@ -0,0 +1,11 @@
+DELETE {
+  GRAPH  <http://mu.semte.ch/graphs/organisatieportaal> {
+    ?s ?p ?o
+  }
+}
+ WHERE {
+  GRAPH  <http://mu.semte.ch/graphs/organisatieportaal> {
+    ?s a <http://mu.semte.ch/vocabularies/ext/ReasonCode>;
+        ?p ?o.
+  }
+}
--- a/config/migrations/20220120101318-insert-new-reasons.sparql
+++ b/config/migrations/20220120101318-insert-new-reasons.sparql
@@ -0,0 +1,37 @@
+PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
+PREFIX ext: <http://mu.semte.ch/vocabularies/ext/>
+PREFIX mu: <http://mu.semte.ch/vocabularies/core/>
+
+ INSERT DATA {
+  GRAPH  <http://mu.semte.ch/graphs/organisatieportaal> {
+    <http://data.lblod.info/id/information-request-reason/3aeec145-acf3-4b6e-9c00-5b8e285736e0> a ext:ReasonCode,
+        skos:Concept;
+        mu:uuid "3aeec145-acf3-4b6e-9c00-5b8e285736e0";
+        skos:prefLabel "Aanmaken van een persoon".
+
+    <http://data.lblod.info/id/information-request-reason/3beec145-acf3-4b6e-9c00-5b8e285736e1> a ext:ReasonCode,
+        skos:Concept;
+        mu:uuid "3beec145-acf3-4b6e-9c00-5b8e285736e1";
+        skos:prefLabel "In het kader van administratief toezicht".
+
+    <http://data.lblod.info/id/information-request-reason/3beec145-acf3-4b6e-9c00-5b8e285736e2> a ext:ReasonCode,
+        skos:Concept;
+        mu:uuid "3beec145-acf3-4b6e-9c00-5b8e285736e2";
+        skos:prefLabel "In het kader van een screeningsdossier".
+
+    <http://data.lblod.info/id/information-request-reason/3beec145-acf3-4b6e-9c00-5b8e285736e3> a ext:ReasonCode,
+        skos:Concept;
+        mu:uuid "3beec145-acf3-4b6e-9c00-5b8e285736e3";
+        skos:prefLabel "In het kader van een erkenningsdossier".
+
+    <http://data.lblod.info/id/information-request-reason/3beec145-acf3-4b6e-9c00-5b8e285736e4> a ext:ReasonCode,
+        skos:Concept;
+        mu:uuid "3beec145-acf3-4b6e-9c00-5b8e285736e4";
+        skos:prefLabel "In het kader van een wijzigingsdossier".
+
+    <http://data.lblod.info/id/information-request-reason/3beec145-acf3-4b6e-9c00-5b8e285736e5> a ext:ReasonCode,
+        skos:Concept;
+        mu:uuid "3beec145-acf3-4b6e-9c00-5b8e285736e5";
+        skos:prefLabel "In het kader van een informatie-uitwisseling (cfr. protocol) met een overheidsinstelling".
+  }
+}
--- a/config/resources/change-events.json
+++ b/config/resources/change-events.json
@@ -58,7 +58,7 @@
      "attributes": {},
      "relationships": {
        "resulting-organization": {
-          "predicate": "org:organization",
+          "predicate": "ext:resultingOrganization",
          "target": "organizations",
          "cardinality": "one"
        },
--- a/config/resources/domain.json
+++ b/config/resources/domain.json
@@ -311,7 +311,7 @@
          "inverse": true
        },
        "change-event-results": {
-          "predicate": "org:organization",
+          "predicate": "ext:resultingOrganization",
          "target": "change-event-results",
          "cardinality": "many",
          "inverse": true
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -158,7 +158,7 @@ services:
    restart: always
    logging: *default-logging
  frontend:
-    image: lblod/frontend-contact-hub:1.5.0
+    image: lblod/frontend-contact-hub:1.5.2
    volumes:
      - ./config/frontend/add-x-frame-options-header.conf:/config/add-x-frame-options.conf
    environment:
Author	SHA1	Message	Date
Nordine Bittich	f41430b699	bump frontend	2022-01-26 15:43:11 +01:00
Sam Van Campenhout	422e92a343	Temporarily rename the change-event-result organization relationship (#94 ) This relationship uses the same `org:organization` predicate that is also used for the local involvements relationship. When querying for local involvements data when an organization also has change events data, mu-cl-resources receives the change events data instead and runs into errors. This is likely a bug in the micro service itself. Renaming the predicate is a quick workaround so we have more time to find the real solution for the problem without a broken app.	2022-01-25 20:04:18 +01:00
Nordine Bittich	b5a7eb1755	bump frontend	2022-01-24 11:28:47 +01:00
claire-lovisa	a3478e997c	Merge pull request #93 from lblod/features/new-reasons-code add new reason code	2022-01-20 14:53:33 +01:00
Nordine Bittich	7aa969c17b	add new reason code	2022-01-20 10:27:55 +01:00