uk-parliament-data-parliament-uk-datasets

Map legacy UK Parliament dataset names to REST API endpoints and Linked Data API paths.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/danbri/forgetmenot --skill uk-parliament-data-parliament-uk-datasets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uk-parliament-data-parliament-uk-datasets
Source: https://github.com/danbri/forgetmenot/tree/main/skills/data-parliament-uk-datasets
Command: npx skills add https://github.com/danbri/forgetmenot --skill uk-parliament-data-parliament-uk-datasets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the complexity of navigating the fragmented UK Parliament data landscape by mapping legacy portal dataset names to their modern API equivalents or Linked Data API paths.

Core Features & Use Cases

  • Dataset Mapping: Instantly translates human-readable dataset names from the explore.data.parliament.uk portal into actionable API endpoints or LDA slugs.
  • Unified Access: Provides a clear path to access parliamentary data, whether through modern REST APIs or the legacy Linked Data API for datasets without modern replacements.
  • Use Case: When a user asks for information on Briefing Papers or the Parliament Thesaurus, this skill identifies the correct data source and provides the necessary path to retrieve the information.

Quick Start

Use the uk-parliament-data-parliament-uk-datasets skill to map the dataset name Briefing Papers to its corresponding Linked Data API path.

Frequently Asked Questions about uk-parliament-data-parliament-uk-datasets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the correct REST API endpoint for a UK Parliament dataset?

To find the correct REST API endpoint for a UK Parliament dataset, map the human-readable dataset name from the explore.data.parliament.uk portal to its modern API equivalent or Linked Data API path.

What is the best way to access UK Parliament briefing papers programmatically?

Accessing UK Parliament briefing papers programmatically requires mapping the dataset name to its corresponding Linked Data API path, which provides a standardized URI lookup for retrieving the information.

Can I still use legacy Linked Data API paths for parliamentary research?

Yes, you can use legacy Linked Data API paths for parliamentary research when a specific dataset lacks a modern REST API replacement, ensuring continued access to archival data.

Are dependencies required to query the Parliament Thesaurus through open data APIs?

No external dependencies are required to query the Parliament Thesaurus; you simply need the correct dataset name to resolve its corresponding Linked Data API path for standardized URI lookups.

Why does navigating the UK Parliament open data landscape require identifier mapping?

Navigating the UK Parliament open data landscape requires identifier mapping to resolve fragmentation, translating legacy portal dataset names into actionable modern REST API endpoints or LDA slugs.

How do I resolve a legacy data.parliament.uk dataset name to an LDA slug?

Resolve a legacy data.parliament.uk dataset name to an LDA slug by using the dataset mapping feature, which instantly translates the human-readable name into the correct Linked Data API path.