A new bug fix release was made for the
`construct-organization-relationships-service`. This release is fully backward
compatible and requires no further changes.
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.
The migrations importing the public OCMW association's contact data contained a
faulty query that matched on empty KBO numbers. As a result contact data was
incorrectly inserted to some AGBs that also do not have a KBO number. This
migration removes the incorrect data.
The migrations importing the public OCMW association's address data contained a
faulty query that matched on empty KBO numbers. As a result address data was
incorrectly inserted to some AGBs that also do not have a KBO number.
This migration removes the incorrect data, which as inserted into the
triplestore next to actual address. Furthermore, this also (re-)inserts the
correct provinces for the affected AGBs.
Removed incorrect queries that match on empty KBO numbers. This is to avoid the
same incorrect data being imported in case the migration is executed again at
some point.
* `organizations` and `organizations-public-info`
- Add the new type of registered organisations to the export configuration
* `public`
- Use a migration to add the classification codes of all recently onboarded
classes of organisations to the `concept-scheme` used by the producer. These
were not added during the initial onboarding:
This includes:
+ public OCMW associations
- Welzijnsvereniging
- Autonome verzorgingsinstelling
+ private OCMW associations
- Ziekenhuisvereniging
- Vereniging of vennootschap voor sociale dienstverlening
- Woonzorgvereniging of woonzorgvennootschap
+ PEVAs
- PEVA gemeente
- PEVA province
- Add the new type of registered organisations to the export configuration
The initial version of the migration to import related organisations only
matched based on KBO numbers. This risks including resources from the type
`ext:KboOrganisatie` as participants. The migration was regenerated including an
additional `FILTER` to exclude organisations of that type from matching.
