@aborruso/ckan-mcp-server 0.4.11 → 0.4.14

package/openspec/changes/archive/2026-01-19-update-repo-owner-ondata/tasks.md

@@ -0,0 +1,12 @@
+## 1. Documentation and Links
+- [x] 1.1 Inventory repo URL references (README, docs, issue templates, web GUI).
+- [x] 1.2 Update GitHub repository links to the ondata org.
+- [x] 1.3 Update any badges and external links that embed the old owner.
+
+## 2. Deployment Guidance
+- [x] 2.1 Update deployment docs that reference the old GitHub repo.
+- [x] 2.2 Validate GitHub Pages URL references where applicable.
+
+## 3. Verification
+- [x] 3.1 Confirm npm scope and publish instructions remain unchanged.
+- [x] 3.2 Run openspec validation and address any issues.

package/openspec/specs/ckan-insights/spec.md

@@ -11,9 +11,13 @@ The system SHALL maintain this specification to document dataset insight tools w
 - **THEN** their requirements are captured in this specification
 
 ### Requirement: Find relevant datasets
-The system SHALL provide a `ckan_find_relevant_datasets` tool that accepts `server_url`, `query`, `limit`, and optional weights for title, notes, tags, and organization, and returns the top N datasets ranked by score with a per-field score breakdown.
+The system SHALL provide a `ckan_find_relevant_datasets` tool that accepts `server_url`, `query`, `limit`, optional weights for title, notes, tags, and organization, and an optional search parser override, and returns the top N datasets ranked by score with a per-field score breakdown.
 
 #### Scenario: Ranked results returned
 - **WHEN** the tool is invoked with a query and limit
 - **THEN** the system uses `package_search` results to return the top N datasets with numeric scores and field contributions
 
+#### Scenario: Search parser override applied
+- **WHEN** the tool is invoked with a search parser override
+- **THEN** the system applies the override to the underlying `package_search` query
+

package/openspec/specs/ckan-search/spec.md

@@ -0,0 +1,16 @@
+# ckan-search Specification
+
+## Purpose
+TBD - created by archiving change update-search-parser-config. Update Purpose after archive.
+## Requirements
+### Requirement: Package search parser override
+The system SHALL support a per-portal default and a per-request override to force package search queries through the `text` field when needed.
+
+#### Scenario: Portal default applies
+- **WHEN** a portal is configured to force the text-field parser
+- **THEN** `ckan_package_search` uses `text:(...)` for non-fielded queries by default
+
+#### Scenario: Request override applies
+- **WHEN** a client explicitly requests the text-field parser
+- **THEN** `ckan_package_search` uses `text:(...)` regardless of portal defaults
+

package/openspec/specs/mcp-prompts/spec.md

@@ -0,0 +1,26 @@
+# mcp-prompts Specification
+
+## Purpose
+TBD - created by archiving change add-mcp-prompts. Update Purpose after archive.
+## Requirements
+### Requirement: Guided prompts are available
+The system SHALL expose a set of guided MCP prompts for common CKAN discovery workflows.
+
+#### Scenario: User requests a guided search prompt
+- **WHEN** a client lists MCP prompts
+- **THEN** the guided prompts are returned with name, description, and parameters
+
+### Requirement: Prompt output includes tool usage instructions
+Each guided prompt SHALL produce instructions that reference the appropriate CKAN tools and parameters.
+
+#### Scenario: Prompt generation for thematic search
+- **WHEN** the user generates a prompt for a specific theme and format
+- **THEN** the output includes the correct tool name and required parameters
+
+### Requirement: Prompt content is localized and consistent
+Guided prompts SHALL use consistent language and parameter naming aligned with CKAN tool schemas.
+
+#### Scenario: Prompt content consistency
+- **WHEN** a prompt is generated
+- **THEN** parameter names match the tool schema (e.g., `server_url`, `q`, `fq`, `rows`)
+

package/openspec/specs/mcp-resources/spec.md

@@ -84,11 +84,37 @@ The system SHALL return resource content as JSON with standard MCP resource resp
 - **THEN** response is truncated to CHARACTER_LIMIT with truncation indicator
 
 ### Requirement: Resource Discovery
-
-The system SHALL list available resource templates when client requests resource list.
+The system SHALL list available resource templates when client requests resource list, including dataset, resource, organization, and dataset filter templates (group, organization, tag, format).
 
 #### Scenario: List resource templates
-
 - **WHEN** client calls `resources/listTemplates`
-- **THEN** server returns list of available URI templates with descriptions
+- **THEN** server returns list of available URI templates with descriptions, including the dataset filter templates
+
+### Requirement: Group Datasets Resource Template
+The system SHALL expose a resource template for accessing CKAN datasets by group via the URI pattern `ckan://{server}/group/{name}/datasets`.
+
+#### Scenario: Read datasets by group
+- **WHEN** client reads `ckan://dati.gov.it/group/governo/datasets`
+- **THEN** server returns JSON with the matching datasets from `package_search`
+
+### Requirement: Organization Datasets Resource Template
+The system SHALL expose a resource template for accessing CKAN datasets by organization via the URI pattern `ckan://{server}/organization/{name}/datasets`.
+
+#### Scenario: Read datasets by organization
+- **WHEN** client reads `ckan://dati.gov.it/organization/regione-toscana/datasets`
+- **THEN** server returns JSON with the matching datasets from `package_search`
+
+### Requirement: Tag Datasets Resource Template
+The system SHALL expose a resource template for accessing CKAN datasets by tag via the URI pattern `ckan://{server}/tag/{name}/datasets`.
+
+#### Scenario: Read datasets by tag
+- **WHEN** client reads `ckan://dati.gov.it/tag/turismo/datasets`
+- **THEN** server returns JSON with the matching datasets from `package_search`
+
+### Requirement: Format Datasets Resource Template
+The system SHALL expose a resource template for accessing CKAN datasets by resource format via the URI pattern `ckan://{server}/format/{format}/datasets`.
+
+#### Scenario: Read datasets by format
+- **WHEN** client reads `ckan://dati.gov.it/format/csv/datasets`
+- **THEN** server returns JSON with the matching datasets from `package_search` filtered by resource format
 

package/openspec/specs/repository-metadata/spec.md

@@ -0,0 +1,19 @@
+# repository-metadata Specification
+
+## Purpose
+TBD - created by archiving change update-repo-owner-ondata. Update Purpose after archive.
+## Requirements
+### Requirement: Canonical repository ownership references
+The project documentation and UI MUST reference the canonical repository under the ondata organization once the repository is migrated.
+
+#### Scenario: Repository references updated
+- **WHEN** a user follows documentation or UI links to the repository
+- **THEN** the links point to the ondata organization repository URL
+
+### Requirement: NPM package ownership remains personal
+The project MUST continue to document the npm package under the @aborruso scope unless an explicit npm ownership change is approved.
+
+#### Scenario: npm install instructions unchanged
+- **WHEN** a user follows installation instructions
+- **THEN** the package name remains @aborruso/ckan-mcp-server
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aborruso/ckan-mcp-server",
-  "version": "0.4.11",
+  "version": "0.4.14",
   "description": "MCP server for interacting with CKAN open data portals",
   "main": "dist/index.js",
   "type": "module",

package/private/commenti-privati.yaml

@@ -0,0 +1,14 @@
+# File YAML per commenti privati su ckan-mcp-server
+# Ogni elemento rappresenta un commento ricevuto
+- autore: Giovanni Pirrotta
+  data: 2026-01-19
+  modalità: telegram
+  testo: >
+    Ciao Andy, se non lo hai già fatto secondo me dovresti contattare AGID. È uno strumento così potente da meritare massima visibilità, non solo per le PA, ma soprattutto per chi oggi fa fatica a trovare dati o a interagire con i portali opendata. Vedo grandissime potenzialità!!
+- autore: Matteo Fortini
+  data: 2026-01-18
+  modalità: call
+  testo: |
+    Ho visto il video, molto interessante, lo proverò e lo racconterò.
+    Ti confesso che quando vedo queste cose mi chiedo se si possa implementare un meccanismo di feedback per ottenere lo stesso risultato con meno risorse. Intendo "come miglioreresti questo sito/API per renderlo più efficiente per queste cose?"
+    In generale a me piacerebbe che la IA pian piano venisse usata per "oliare" le interazioni, adesso la stiamo usando come una schiava per fare le cose scomode