search

eclipse-tractusx / bpdm

bpdm
Apache License 2.0
5 stars 15 forks source link

Integration of GLEIF Codes in Meta Data Controller for BPDM Pool #784

Open HeyHardy opened 4 months ago

HeyHardy commented 4 months ago

As a sharing member, to align with global standards and enhance the interoperability of the Catena-X platform, I need to implement the GLEIF Entity Legal Forms (ELF) codes into the metadata controllers of both the Gate and Pool services. This integration is crucial for:

nicoprow commented 2 weeks ago

@HeyHardy Do we have some information about the license of this code list? We would need to reference the source together with the license if we want to integrate the list into our Pool.

nicoprow commented 2 weeks ago

As it was stated here https://www.gleif.org/en/about/open-data I will be taking the CC0-1.0 license for the data

nicoprow commented 2 weeks ago

As a sharing member, to align with global standards and enhance the interoperability of the Catena-X platform, I need to implement the GLEIF Entity Legal Forms (ELF) codes into the metadata controllers of both the Gate and Pool services. This integration is crucial for:

* [ ]  Standardization: Adopt ISO 20275 ELF codes for legal entity identification.

* [ ]  Enhanced Metadata: Include GLEIF codes in entity metadata for accurate legal form representation.

* [ ]  Improved Interoperability: Facilitate data exchange and verification across global platforms.

* [ ]  Data Quality: Support service providers in elevating data quality and reliability.

* [ ]  Testing: to ensure running E2E test

* [ ]  start with countries related the golive (inital load waves)

@HeyHardy @Sebastian-Wurm

The Gleif code list has a lot of columns and we need to make sure which information we want to overtake for the legal forms.

The legal forms model currently is quite simple and only has these fields:

  1. Technical Key
  2. Name
  3. Abbreviation

My suggestion for mapping the information from the code list:

  1. Technical Key -> "ELF Code"
  2. Name -> "Entity Legal Form name Local name"
  3. Abbreviation -> "Abbreviations Local language"

There is also transliterated versions for name and abbreviation available.

What is your opinion?

Sebastian-Wurm commented 2 weeks ago

Let's discuss a proposal for a comprehensive solution being able to fulfill future UI input / filtering requirements. It should include:

Note that in this proposal "TechnicalKey" and "Language" would be a compound key, as there are multiple entries for the same ELF code having different names and abbreviations for different languages, that are official languages in that country, e.g. for Canada it's English and French, for Finland it's Finnish and Swedish.

Note that the ELF code can be issued either on country level or on the level 1 of the administrative areas.

Note that the ELF code has multiple approved abbreviations, separated by a semicolon.

image