The Vlaamse Gemeenschapscommissie is a special kind of administrative unit, with
its own specific classification code (which was added in a previous commit). The
core data, address, and contact information was provided by the business.
Note: currently the province in the address is intentionally left empty. This
data will be provided (or entered) later by business.
A new bug fix release was made for the
`construct-organization-relationships-service`. This release is fully backward
compatible and requires no further changes.
The municipality of Borsbeek will merge with the municipality Antwerp as of
01-01-2025. This will result in a new district Borsbeek part of municipality
Antwerp.
This migration adds that new district such that a URI is assigned to it and its
governing bodies are created. The information available at this time is limited
its (legal) name. Other core data, such as identifiers, and further information
such as site addresses will be added later by business.
- The previous version of the migrations lacked the triple actually linking the
new organisations with the placeholder for SharePoint identifier. This triple
was now added.
- Ensure the timestamp prefixes are unique by adding 1 second delay in between
generating each migration.
As part of the municipality mergers for 2025, four new municipalities and their
corresponding OCMWs will have new KBO numbers. Consequently, these organizations
need to be fully manually created.
This commit adds the migrations to import the organisations for the merged
municipalities and OCMWs such that their URIs can already be shared among
applications.
The currently imported data concerns:
- core data such as (legal) name, region, status, KBO, and OVO number
- the necessary governing bodies, with as starting date 2025-01-01
The NIS-codes (and associated data) will be added in future migrations when the
NIS2025 update has been released.
Other missing data, such as addresses and contact details, will be added later
on by business.
The Vlaamse Gemeenschapscommissie is a special kind of administrative unit, with
its own specific classification code (which was added in a previous commit). The
core data, address, and contact information was provided by the business.
Note: currently the province in the address is intentionally left empty. This
data will be provided (or entered) later by business.
There was an issue with the old producers not taking into account all
graph filters, thereby exporting sometimes too many triples.
Note: please consider moving these old producers to the latest
one. (It should be a matter of shuffling config around)
- Remove relations based on the `org:hasSubOrganization` predicate.
- Migrate triples for the `org:hasSubOrganization` predicate to new, appropriate
triples.
- Remove relations based on `ext:isFounderOfOrganization` predicate from the
data model.
- Migrate the `ext:isFounderOfOrganization` triples to new, appropriate triples.
- add the missing original organisation and matching change event result to one
merger change event
- remove the superfluous merger change event, except for its reused change event
result
The original migration to import the participants for public OCMW associations
contained a bug causing it to not match municipalities. More specifically:
- the type triple for municipalities is located in the `shared` graph;
- consequently the `FILTER EXISTS` statements to limit matches to administrative
units could not succeed for municipalities as the queries are limited to the
`administrative-unit` graph.
This new migration fixes this problem by changing the `FILTER EXISTS` into a
`FILTER NOT EXISTS` to exclude resourses of type `ext:KboOrganisatie`.
The migration importing related organizations for public OCMW associations was
incorrect in that it did not exclude resources of type `ext:KboOrganisatie`
being matched. This migration removes all incorrectly inserted triples.
