RSSChangelog

See updates across the data model, metadata structure, and API of our service. Breaking changes that require updates to data consumer applications are announced prior to their implementation.

Filter by components: Metadata (1) · Data model (3) · Datasets (1) · yente (1)

#1 Splitting Person nationality and citizenship

Effective date:
Components affected:Data model
Announcement:

The followthemoney data model currently stores the citizenship of individuals in the nationality property. After being advised the the two concepts are not identical in some jurisdictions, we've now also introduced a citizenship property. From the effective date we will begin moving country affiliations for individuals in the citizenship property if that nomenclature is used in the data source (e.g. the UK sanctions list).

Data consumers should check both properties in the future. To get a complete picture of the countries linked to an individual you may also want to check the birthCountry and country field. The latter serves as a catch-all field for affiliations that may not involve citizenship or holding a passport - simple residence might be enough.

See: Person schema.

#5 permId property moved up in hierarchy

Effective date:took effect on
Components affected:Data model
Announcement:

The permId property for LSEG/Refinitiv company codes has been moved up from the Company to the Organization schema to enable reflecting government entities (using the PublicBody schema) also receiving these identifiers.

#6 Length limit to be added for property values

Effective date:took effect on
Components affected:Data model
Announcement:

A soft length limit in Unicode codepoints has been added for all properties. These can be seen in the data dictionary. The goal of this is to make it easier for data consumers to import our data into systems with fixed-length column types.

Property values are not yet guaranteed to be limited to this value, but our tooling now alerts us when values are longer than this, so that we can identify sources which don’t adhere to sensible limits and eventually enforce hard limits.

Imposing a length limit has also identified many instances where the data required further cleaning, which we've implemented as needed.