Sports Data

1.3.1 - 2026-11-09

  • Fixed: Opening Additional Information, Provider References or a season's attributes in Season History showed a blank page in host apps running React 17. The widget no longer uses a React 18-only API there

1.3.0 - 2026-11-06

  • Added: Volleyball. Volleyball entities (vb: IDs, sport VOLLEYBALL) can be browsed, filtered by sport, created and imported from JSON like any other sport. Volleyball competitions are contested by teams, so their participant type is always TEAM
  • Fixed: Searching with a sport selected returned matches from every sport. The search now respects the sport filter
  • Fixed: Creating an entity showed no confirmation. It now shows the created message for the global catalogue or for the client
  • Added: Attribute values in Additional Information can be translated. The translate button in a value field opens the value's translations: add a language and type the value in it. Translations are stored per language in the attribute's labels, and a language left empty is dropped on save
  • Fixed: Editing the attributes in Additional Information or Season History removed the labels already stored on every attribute. They are now kept
  • Changed: Attribute names that ingestion stored as English translations (en "Position" on POSITION, en "Date of Birth" on BIRTHDATE) are removed when an entity is opened, and the cleaned attribute is written the next time the entity is saved
  • Changed: Import JSON documents an attribute's labels as translations of its value
  • Added: Keyboard support in searchable selects. In the Related and Season History link search and in Add language, the arrow keys move the highlight, Enter picks the highlighted option, and Tab picks it and moves on. Esc clears the link search
  • Changed: Searchable selects use one highlight for mouse and keyboard, and Add language shows each language's flag and code

1.2.0 - 2026-10-07

  • Added: Platform operators can create an entity from JSON with Import JSON next to Create. Paste the JSON for one entity or drop a .json file of up to 512 KB, pick the entity type and whether it goes to the global catalogue or the client's own data, and review it before creating. The JSON is checked as it is typed: invalid or unknown properties are listed with the reason and left out, and only a missing or invalid required field blocks creation. Each problem points to its line in the JSON. The ID is always generated, as when creating in the form, and an ID in the JSON is ignored. A field reference and an example for each type are shown alongside
  • Changed: Creating in the form and creating from JSON write the entity through the same code, so both produce the same document
  • Added: Season History has a Paste JSON button. Paste a list of seasons, a single season or a whole entity's JSON, and choose whether it merges with the existing seasons (a season with the same season_id is replaced) or replaces them all. Seasons are checked as the form checks them, invalid seasons and links are listed and left out, and nothing is saved until the entity is saved. Available to anyone who can edit the entity

1.1.1 - 2026-10-06

  • Changed: A platform operator creating a new entity in the Catalogue can edit its ID, so an entity can keep the ID it already has in another sport data source. The ID still starts out generated, must match the entity type's format and must not already exist. Everywhere else - editing an existing entity, creating in Overrides, or a client admin - the ID stays locked
  • Added: Teams have a Tertiary brand color
  • Added: Athletes have Date of Birth and Position fields in General
  • Added: Venues can be linked to a country in Related
  • Changed: Entities are saved with every field the Search API returns for their type, so a new or edited entity has the same shape as one imported from a data provider. Fields with no value are saved as null or an empty list instead of being left out, and every entity carries its content_type, participant_type and a Fans United provider reference
  • Changed: The GENDER search filter follows the entity's gender, so new entities can be filtered by gender and a changed gender is no longer indexed under the old value
  • Changed: An entity's country is edited as a Country link in Related and saved to country_id as well. Teams imported from a provider, which held their country only in country_id, now show it there
  • Changed: Translations are saved with uppercase language codes, and a cleared field is saved as null instead of an empty string. Athlete translations stored as shortName and threeLetterCode are shown and saved as short_name and three_letter_code
  • Changed: A country's Type offers Political and Sport, the values countries are actually stored with
  • Fixed: Saving a team imported from a provider removed its COUNTRY search filter, so filtering by country no longer found it
  • Fixed: An entity saved by an older editor without a top-level sport is saved with one again

1.1.0 - 2026-09-28

  • Added: Related entities can be dragged into order, and are saved and returned by the Search API in the order shown. In Related they are ordered within their relationship group; in Season History, anywhere in the season's list
  • Added: Season History links show the linked entity's name, picture and ID, are added with the same search as Related, and carry a tag naming their relationship. A link whose ID matches no entity falls back to editable relationship and ID fields
  • Added: relatedReorder label for the drag handle tooltip
  • Added: Tennis competitions have a Participant Type - Singles, Doubles or Team - defaulting to Singles
  • Changed: seasonAddLink now adds a link by typing its ID, and defaults to "Add by ID instead"
  • Changed: Competitions in every other sport are always saved with a participant type of Team, and the field is not shown for them
  • Removed: seasonRelationshipColumn label, as season links no longer have column headings
  • Removed: Formula 1, from the sport filter, the Sport field and entity ID validation
  • Fixed: The "Feature disabled!" card flashed briefly on sign-in and on reload for users who do have access. The widget now waits for the user's roles before deciding
  • Fixed: A dropdown field stored with a value its options do not list showed as blank. The stored value is now shown

1.0.1 - 2026-09-23

  • Fixed: Related entities of an overridden entity all showed as "Unknown entity". A link is now resolved from the global catalogue whenever the client's own overlay cannot answer for it, including when that overlay does not exist yet
  • Fixed: Save could stay disabled with nothing on screen explaining why. Validation errors an entity was already stored with are now shown as soon as it opens, and the section rail marks the section holding them
  • Fixed: An entity stored without a popularity could not be saved at all. It now opens with a default of 80, which reads as an unsaved change, and a newly created override is written with one
  • Fixed: A season could be saved without an ID, leaving a season nothing could resolve back to a competition. A season ID is now required, and the field explains how to build one
  • Fixed: An uploaded image could appear broken after saving. The preview now uses the address the upload itself returns, and an image the editor cannot load says so instead of showing a broken-image icon
  • Plainer wording in the Assets section describing how an image is stored and what apps receive

1.0.0 - 2026-09-17

  • Initial Release:
    • Browse the global sport catalogue across seven entity types, with search, sport filter and pagination
    • Create and edit entities, with per-type sections for translations, assets, branding, socials, related entities, season history, additional information and provider references
    • Client overrides: create one from a row or several at once, see which fields differ from the global entity, and remove an override to fall back
    • "How people find this entity" panel explaining name matching, variations, filterable links and popularity ranking
    • Read-only JSON preview of the entity data being saved
    • Role-aware UI for platform_operator and client_admin

Did this page help you?