🆔Organisation names

To comment on a FP:

Date, name: comment

Status Feature Passport

STATUSOWNERDATE

In proposal

Sofie

11, 13 en 14/02/2024

In refinement - Design Research

In refinement - Technical Research/Feedback

DEV (OP + CLB) meeting on 13/02/2024

In development

In QA/ Testing

In Final state

Epic: OP-2286: Different types of organisation names

ANALYSIS

This part of the feature passport is owned by the analyst

Current state

For all organisations in OP we used the names that were provided in the SharePoint lists. We use different names throughout our applications for different reasons. We want consistent using of names. This can also prevent users from recreating existing organisations because they are known under a different name.

Application profile: Organisatie Basis

At the moment we have one name in OP modelled as voorkeursnaam (http://www.w3.org/2004/02/skos/core#prefLabel)

OSLO standard

The application profile Organisatie Basis has 3 types of names

Class Organisation (Organisatie)

Class Registered Organisation (Geregistreerde Organisatie)

Use of OSLO names

Original Github discussion in dutch: https://github.com/Informatievlaanderen/OSLO-Discussion/issues/397

Snippet of name discussion on Github

The principle of Multiple Classification applies: Organisations can be classified in multiple ways. In the AplicationProfile Organisation even in 4 ways: according to

  1. whether the Organisation is a Formal (or even Registered) Organisation.

  2. whether it is an Organisational Unit or not.

  3. whether it is a Collaborative Organisation or not.

  4. whether it is a PublicOrganisation or not.

These classification systems are disjoint, you can combine them. a few examples:

  • A Registered, PublicOrganisation

  • An Organisational Unit that is also a PublicOrganisation

  • A Collaborative that is Registered

  • Etc

The City/Municipality of Antwerp is simultaneously a PublicOrganisation and a RegisteredOrganisation.

Specializations

RegisteredOrganisation.legalName is actually a specialisation of Organisation.preferredName (in the context of e.g. the KBO, the preferred name is the one established at legal registration).

In PublicOrganisation, PreferredName is not specialised, so we simply inherit PreferredName there (the name preferred by the PublicOrganisation, since a PublicOrganisation is an official body we can say that it is the official name). And so Antwerp can have two names: as a RegisteredOrganisation we call it "City of Antwerp", officially, however, it is (municipality) "Antwerp".

See Miro: Frame Modeling of names

Problems

1. We now use pref label for name

At the moment we have the name in OP modelled as voorkeursnaam (http://www.w3.org/2004/02/skos/core#prefLabel)

Snippet of name discussion on Github

The term preference can indeed be interpreted in different ways, but we can assume here that it is the preference of the Organisation itself. If you prefer a name yourself, I fear it is more likely to be an alternativeName then.

For registered organisations, we can assume that the preferred name of the organisation is the one they register in KBO.

  • All organisations in OP are registered organisations and they have a KBO number

  • voorkeursnaam = wettelijke naam (= name registered in KBO)

2. Wettelijke naam is not always registered the correct way in KBO

Wettelijke naam is translated as legal name.

In KBO the organisation have to register the name juridical name (guideline naming in KBO)

In the OSLO description it is assumed that the organisations register the juridical name. In reality, organisations register the preferred name.

Example for Gent (gemeente)

  • Legal naam (registered in KBO) = Stad Gent

  • Juridical name = Gent

Analysis see Miro: Comparisons of KBO naming + see the conclusion in Gitbook of a usertesting of the filters (Users mentioned names in OP not being the same as in the Notulen) + check analysis on worship services

Snippet of name discussion on Github

By "wettelijk" (= legal) here, according to the definition, we should mean the name assigned at the time of legal registration (which is different from juridical).

3. We need a 'Juridical name' which is not available in OSLO

This new name will solve the problem we have with the 'Wettelijke naam'

  • Description Juridical name: name from statutes, decrees or other legal regulatory texts or decisions

  • Omschrijving Juridische naam: naam uit de statuten, decreet of andere juridisch regelgevende teksten of besluiten

🤩 Expectations

We want to register the correct names in OP. The goal in the long term is to help KBO have an up-to-date database and the correct use of names.

Previous thoughts > not applicable anymore

Names in tab 'ABB gegevens' on 'kerngegevens' page

  • Naam (= preferred name within ABB) We will use this name to sync within the ABB ecosystem.

    • Non-editable field in OP

    • Autofill value, business rule:

      • Juridische naam

      • If no 'Juridische naam' is available, display 'Wettelijke naam'

    • This field can not be empty

CLB contactapp: We will not show this field in CLB contact app.

  • Juridische naam (= legal name)

    • Only editable during the creation of an organisation.

    • Once the organisation is saved, the field becomes a non-editable field in OP, except for Gemeente, OCMW, District, Provincie, Politiezone and Hulpverleningszone (field is still editable)

CLB contactapp:

  • Non-editable field for Gemeente, OCMW, District, Provincie, Politiezone and Hulpverleningszone

  • Editable field for all other organisations (except for the organisation that don't have access to the CLB contactapp.)

  • Alternatieve naam (= alternative name)

    • Not editable for Gemeente, OCMW, District, Provincie, Politiezone and Hulpverleningszone (CLB contact app will use the data from OP via a 1x sync. If this data changes in OP, then the developers have to change this in CLB contact app via the backend.)

    • Editable for all the other organisations in OP by the organisations themselves via the CLB contact app!

1) Names in tab 'ABB gegevens' on 'kerngegevens' page

  • Naam (= preferred name within ABB) We will use this name to sync within the ABB ecosystem.

    • This field, must have a value, thus can not be empty

    • Autofill value, business rule:

      • Juridische naam

      • If no 'Juridische naam' is available, display 'Wettelijke naam'

    • Not editable field

  • Juridische naam (= legal name)

    • Not mandatory field

    • Editable during the creation of the organisation

    • Editable after creation? This depends on type of organisation (see table below)

  • Alternatieve naam (= alternative name)

    • Not mandatory field

    • Editable during the creation of the organisation

    • Editable after creation? This depends on type of organisation (see table below)

TO DISCUSS with Yassin on the worship services part:

  • analysis on worship services

  • Prefill alternatieve naam (= copy of voorkeursnaam) for worship services data that is already present in the OP? TO discuss with Yassin

2) Names in tab 'KBO gegevens' on 'kerngegevens' page

= Solved via Epic: OP-2731: Integration: show KBO data in OP

🤔 Discussion points

1) How to model the different names?

https://binnenland.atlassian.net/browse/OP-2316

DEV meeting 13/02/2024: We will use the three names available in the OSLO application profile Organisatie Basis.

We interpret the names a little bit different in tab 'ABB gegevens' and 'KBO gegevens'.

2) Do we have all the 'Juridische namen' of the organisations in OP?

We have the list of 'Juridische namen' (To be delivered by Sofie via OP-2997) of

  • Gemeente

  • OCMW

  • District

  • Provincie

  • Politiezone

  • Hulpverleningszone

The Juridische name of the other organisations in OP has to be filled in by the organisations themselves via the Contact app!

4) Alternative names

Can we add the 'commerciële naam' and 'afgekorte naam' of KBO if available?

DEV meeting 13/02/2024: Non discussion, the data of KBO is already available via the KBO tab page 'kerngegevens'.

5) Filter names

When the search field Naam is used, it should generate results from all name fields of the 'ABB gegevens' tab.

Is it possible to also search in the name fields of the 'KBO gegevens' tab?

DEV meeting 13/02/2024: This should be possible to achieve with elastic search.

6) OP and Contact app

OK to develop this first in OP and then in Contact app?

Changes needed in the OP producer en CLB consumer?

DEV meeting 13/02/2024: Because the edit version of the CLB app isn't live yet, we will develop this in OP first and then in CLB (possibly by the same developer?)

Previous questions/discussions

  • Q: Can we add the field alternatieve naam? A:Yes

  • Q: According to the datamodel the alternatieve naam can have multiple entries [0..1]. How do we handle that? A: We make no distinction in the different alternative names. We consider all other names as alternative names.

  • Q: The field alternatieve naam will be used by Kalliope, instead of the voorkeursnaam. As it will be used by Kalliope, this field can not be empty. How do we solve this?

    • We make the field mandatory: users can copy the voorkeursnaam in the alternatieve naam field if no alternative name is available.

    • We don’t make the field mandatory, but if it's left empty when click on ‘save’ then the system automatically copies the voorkeursnaam.

    • … (other suggestions)

    A: This will be solved within Kalliope, they have their own name field.

  • Q: What can we consider to be the correct voorkeursnaam?

    • Naming in KBO?

    • Naming in statuten?

    • Naming mentioned in besluiten?

    A: It is the name that is preferred by the organisation. In the context of the KBO we can assume that the preferred name is the name that is registered in KBO.

  • Q: When the search field Naam is used, it should generate results from alternatieve and voorkeursnamen. A: TO BE ANALYSED

  • Q: Do we need to add an extra column alternatieve naam in the table of the search page?

    • If yes, this would result in a lot of double names where the alternatieve naam is the same as the voorkeursnaam.

    • If now, results might be shown where the searched string is not part of the voorkeursnaam.

    A: We will not add a new column for now

  • Q: Prefill alternatieve naam (= copy of voorkeursnaam) for worship services data that is already present in the OP? A: TO discuss with Yassin

SOLUTION

The next two parts of the FP can [sometimes] be worked on simultaneously

Design

This part of the feature passport is owned by the designer

Design see Miro: OP > As is - To be (table)

ABB data tab view

ABB data tab edit

KBO data tab view

KBO data tab edit

Not applicable. KBO data can not be edited. We synchronise the data with OrganisatieRegister Wegwijs.

Technical

This part of the feature passport is owned by the technical team

[Information about the technical solutions for expectations that need it - e.g. using mu-search for showing all types of positions in one table.]

After the designer and/or the technical team finish their task, a meeting follows where the solutions are presented. The team exchanges feedback and amends the feature passport where necessary.

PreviousOP-Team: Data Quality Management report (WIP)NextUpdate mechanisms (NL)

Last updated