- 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.
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.
The initial version of these migrations were defined too broadly. Since they
only matched on KBO numbers they also included the KBO organisations, imported
from wegwijs, adding them as participants.
This commit adds extra checks to exclude KBO organisations from being added as a
participant for a public OCMW association. Furthermore, the main migration is
split into two parts to work around an error otherwise encountered when
executing the migration as a single whole.
Forwarding requests on the organizations path to the cache leads to issues were
changes that the user just made are not shown. For example, when adding a
related organization the newly added organization would not show up in the list
unless the cache was restarted.
Soon we want to introduce (additional) non-administrative unit
organizations. This renaming makes it more clear this index is not limited to
administrative units, both here as where it is used in the frontend. Note,
technically the 'units' name was already incorrect as a 'Representatief orgaan'
is not an administrative unit.
The change events related to an organisation contains some data errors:
- There is a change event result without any corresponding change event. This
causes an error when visiting the change events page for this organisation.
- There are two identical change event results for the same change event. This
causes the change event to be shown twice in the table. (Only on PROD)
The added migration removes these unnecessary elements change event results.
