Commit Graph

35 Commits

Author SHA1 Message Date
Claire Lovisa
b89bd61fa6 Fix Heist-op-den-Berg municipality in camel case 2025-11-03 16:49:06 +01:00
Claire Lovisa
eee9f18561 Remove migrations inserting/deleting brussel 2025-07-04 08:47:16 +02:00
Claire Lovisa
0c9355c94f Add migrations to revert Brussels' province and municipality 2025-07-03 11:11:39 +02:00
Claire Lovisa
0e9483b4f8 Move membership to shared graph 2025-06-30 10:22:38 +02:00
Claire Lovisa
e078ae48a7 Remove province-specific properties from municipality location 2025-06-26 15:51:06 +02:00
Claire Lovisa
df8512d8f9 Add brussel municipality via migration 2025-06-25 20:36:37 +02:00
Claire Lovisa
4131395159 Merge branch 'development' into feature/brussels-gewest 2025-06-23 14:42:58 +02:00
mirdono
b31d6c65e6 fix: update label for locations to match their merged municipality
As part of the 2025 municipality mergers, three municipalities kept their URI
but were renamed. This updates the labels for their scope of
operation (nl. werkingsgebied) locations accordingly. This way the label of the
location resources matches the name of the municipality administrative unit.
2025-06-20 12:52:41 +02:00
Claire Lovisa
0be27e1ef2 Add Brussels Hoofdstedelijk Gewest 2025-06-20 10:54:01 +02:00
wolfez
addd4304f6 datafix: delete change event and update status to active for protestantse kerk oostende 2025-05-21 14:04:32 +02:00
wolfez
ba5bdac6cb datafix: update status of kerkfabriek weelde to non-active 2025-05-21 14:03:33 +02:00
Riad Abdallah
eb7d8949cd Remove Active Organization from Inactive CKB Deinze
There is a 'double' instance of CKB Deinze in the database. One is active, and the other is inactive. This confuses systems, and it doesn't make sense that active organizations are linked (almost managed) by an inactive organization.

* Insert suborganization(s) belonging to non-active org to the active one
  * Insert new membership belonging to the suborganization(s) and active org
* Delete memberships for non-active org
2025-05-08 16:26:52 +02:00
wolfderechter
0d87feb119 Remove change events from ckb's and update their status (#535)
* Remove change events from ckb's and update their status

* move status migration to triggering-indexing

* remove unneeded code

* update changelog
2025-04-01 09:42:56 +02:00
felix
5deec6a735 undo name change OCMWv 2025-03-21 17:14:33 +01:00
felix
d246555c8a swapped migration to triggering index migration. 2025-03-21 16:58:37 +01:00
mirdono
b296a99ac0 Merge branch 'master' into development 2025-01-23 20:05:54 +01:00
mirdono
3bc47a7fb0 fix: merger change event between St.-Amandus and Sint-Martinus
The worship service St.-Amandus was not included as `orginalOrganization` in the
merger change event somehow. As a result it was not listed as involved
organisation in the change event details. Furthermore, its status was not
correctly updated to "Not active".
2025-01-21 10:04:23 +01:00
Riad Abdallah
74096c96b1 Merge branch 'development' into cleanup/fully-delete-agb-stekene 2025-01-17 16:24:26 +01:00
Riad Abdallah
5ea8bfc46b Completely remove AGB Stekene data
A previous PR changed the org's status only; this PR completely removes
its data.
2025-01-17 16:00:20 +01:00
mirdono
51e41f1eb1 Merge branch 'master' into development 2025-01-10 10:59:35 +01:00
mirdono
090a69fd3f feat: allow local migrations that trigger indexing
Support for environment-local migrations that trigger indexing. This is similar
to the local migrations for the regular `migrations` service.
2025-01-09 22:32:20 +01:00
mirdono
824201ced6 feat: merge police zones 2025
- Migrations to create the necessary merger change events that represent the
  merger of several police zones into three new ones
- Migration to update the status of the merged police zones to not active
2025-01-09 15:29:54 +01:00
cecemel
b60004fcf2 Merge pull request #486 from lblod/archive-agb-stekene
Archive AGB Stekene
2025-01-03 12:23:39 +01:00
felix
945faf8761 move migrations to trigger-re-index-migration
Don't forget to `drc restart migrations-triggering-indexing`
2025-01-03 12:20:15 +01:00
mirdono
8143aac736 chore: regenerate full addresses to reflect address changes
This migration regenerates the `locn:fullAddress` triples for addresses in a
municipality involved in a merger. In essences this migration updates the
`locn:fullAddress` triple for each address changed by the migrations in the
previous commit.

Notes
- The migration is split over two queries, one for addresses without a box
  number and one for addresses with a box number. This avoids complicating the
  query with conditional logic at the cost of code duplication in the queries.
- In the existing full address triples two different notations are used to
  separate the box and building number. OP currently separates them simply by a
  space, which is what this migration matches for. But some historical data uses
  a dash "-" to separate building and box number. Consequently, this migration
  might match more address resources than strictly updated for the municipality
  merges.
2024-12-19 16:01:47 +01:00
mirdono
dde2e42696 chore: update address municipalities for 2025 municipality mergers
This migration updates the municipality name in the addresses for all
organisations located in a municipality whose name changes due to the 2025
municipality mergers.
2024-12-19 16:01:47 +01:00
mirdono
0f1654e64c chore: move organisations in Zwijndrecht to province East Flanders
As part of the 2025 municipality mergers Zwijndrecht will merge with Beveren and
Kruibeke into Beveveren-Kruibeke-Zwijndrecht. Additionally this means that
Zwijndrecht changes province from Antwerp to East Flanders.

This migration updates the province for each organisation with an address in
Zwijndrecht to East Flanders.
2024-12-19 16:01:47 +01:00
mirdono
477c37320d feat: add merger change events for 2025 municipality mergers
These migrations insert the merger change events that are needed for the 2025
municipality mergers.

The migrations executed by the `migrations` service insert the actual merger
change events for
- mergers where the resulting organisation is a new organisation (these were
  added earlier in #442);
- mergers where the resulting organisation is an already existing, active
  organisation; and
- the special case where the municipality Borsbeek is merging with the
  municipality Antwerp, thereby creating a new district Borsbeek.

The migration executed by the `migrations-triggering-indexing` service updates
the status of the necessary organisations:
- the new municipalities/OCMWs/district are set from "Being founded" (nl. "In
  oprichting") to "Active"
- the other municipalities are changed from "Active" to "Not active"
- organisations that simply remain active before and after the merger are *not*
  updated
2024-12-13 12:36:06 +01:00
mirdono
806a870744 chore: rename municipalities and OCMWs for mergers 2025
As part of the 2025 municipality mergers 3 municipalities, and their
corresponding OCMWs, keep their original URI but do change their name. More
specifically:
- Bilzen becomes Bilzen-Hoeselt
- Ham becomes Tessenderlo-Ham
- Tongeren becomes Tongeren-Borgloon
2024-12-13 12:35:24 +01:00
Claire Lovisa
ca92809cf5 Fix classification of Voetbal in de Stad vzw (#477)
* Fix classification of an organization

* Move migration to trigger indexing on execution
2024-11-20 11:03:56 +01:00
Claire Lovisa
42dc3af86a Fix status and add missing orgaan
I also had to bump mu-search, I was getting HTTP 500 errors otherwise
(NoMethodError - undefined method `each' for nil:NilClass)

About the mandates creation:
 - LidVanRechtswege : shared mandate for all the organen in time
 - Bestuursleden big half : shared with 2023-2026 because 2020 was the start of a big half
 - Bestuursleden small half : new mandate (should have been shared with 2017-2020, but we don't have this time period)
 - Voorzitter : new mandate
 - Secretaris : new mandate
 - Penningmeester : new mandate
2023-03-24 15:34:35 +01:00
Nordine Bittich
0c9024b7c6 Incident/move change event (#251) 2023-03-07 10:58:05 +01:00
Nordine Bittich
160c355d1c Kerkfabriek St.-Antonius van Padua van Gent (Heirnis)” with status “Niet actief” from OP (#241) 2023-02-27 16:13:22 +01:00
Claire Lovisa
4179194e6f Moving migration to trigger reindex 2023-02-07 15:05:26 +01:00
Claire Lovisa
0f7313b944 Add option to create migrations triggering index 2023-02-06 14:37:26 +01:00