MetaMuseum
Menu
← Documentation home

Canonical Markdown source · Jul 6, 2026

Linked Art API: Groups

linked-art/api/groups.md · 61 lines · SHA-256 abbb3e00ba19

Last refreshed: 2026-07-06

Source: Groups endpoint, part of Linked Art API 1.0, published under CC BY 4.0. This is a project summary; the upstream page is authoritative.

Purpose

The Group endpoint describes identifiable sets of actors, including families, organizations, companies, departments, workshops, societies, and other sets of people or subgroups. It is similar to the Person endpoint, with additional fields for group membership and lifecycle.

Required Shape

A Group endpoint record dereferences to one JSON-LD object:

  • `@context`: Linked Art context URI, or an array ending with that URI for extensions.
  • `id`: dereferenceable HTTP(S) URI for the group.
  • `type`: `Group`.
  • `_label`: developer-facing label.
  • `classified_as`: classifications following the `Type` structure, such as society or nationality.
  • `identified_by`: `Name` and/or `Identifier` structures.

Optional Fields

  • `referred_to_by`: statements about the group.
  • `equivalent`: external identities.
  • `representation`: visual works representing the group.
  • `member_of`: parent group membership.
  • `subject_of`: textual works focused on the group.
  • `attributed_by`: relationship assignment evidence.
  • `contact_point`: addresses or contact identifiers.
  • `residence`: associated place.
  • `carried_out`: professional activities of the group.
  • `participated_in`: events or activities in which the group participated but was not responsible.
  • `formed_by`: `Formation` event for the group.
  • `dissolved_by`: `Dissolution` event for the group.

Common Incoming Relationships

  • `member_of` from Person or Group records.
  • `carried_out_by` from activities.
  • `current_owner`, `current_custodian`, and `current_permanent_custodian` from object records.
  • `represents` from visual works.
  • `about` from textual works.
  • `transferred_custody_to` and `transferred_custody_from` from provenance activities.
  • `transferred_title_to` and `transferred_title_from` from provenance activities.
  • `paid_to` and `paid_from` from provenance payment activities.

Meta Museum Notes

Meta Museum already exposes groups through `/api/agents/{id}` and preserves rich `Group` records through `/api/records/{id}`. Existing actor tests cover group contact points, group membership, formation, residence, professional activities, and group classifications. Activity and provenance coverage also uses `Group` references for carried-out-by actors, ownership/custody transfers, payments, and auction houses.

Test Ideas

  • Keep `/api/agents/{id}` role coverage aligned with both `Person` and `Group`.
  • Preserve a `Group` fixture with `contact_point`, `member_of`, `residence`, `carried_out`, `formed_by`, `dissolved_by`, `equivalent`, and `attributed_by`.
  • Preserve incoming provenance references to groups for title transfer, custody transfer, and payment without flattening them into labels.
  • Ensure group nationality and organization type remain `classified_as` terms rather than custom group subclasses.