Skip to main content

A CKAN extension that lets you attach a flexible, schema-free data dictionary (“resource documentation”) to any resource, not just Datastore-backed ones.

Project description

Tests

A CKAN extension that allows attaching a flexible data dictionary (resource documentation) to any resource — not just those backed by the Datastore.

Each resource’s documentation can include a validation schema defined individually using JSON Schema Draft 2020-12, enabling optional enforcement of structure and constraints while maintaining the flexibility of a free-form data dictionary.

The official specification for JSON Schema Draft 2020-12 is available here.

Here is an example of a resource documentation in a format of Datastore fields. But it's not limited to that format, you can save any custom data you need.

Documentation table

It's also possible to define a validation schema for the resource documentation, which will be used to validate the documentation data.

Validation schema

Requirements

Compatibility with core CKAN versions:

CKAN version Compatible?
2.9 and earlier no
2.10+ yes

Installation

To install ckanext-resource-docs:

  1. Activate your CKAN virtual environment, for example:

    . /usr/lib/ckan/default/bin/activate
    
  2. Install the extension from PyPI:

    pip install ckanext-resource-docs
    
  3. Add resource_docs to the ckan.plugins setting in your CKAN config file (usually located at /etc/ckan/default/ckan.ini).

  4. Restart CKAN. For example, if you've deployed CKAN with Apache on Ubuntu:

    sudo service apache2 reload
    

Config settings

The following options control how ckanext-resource-docs behaves.

ckanext.resource_docs.append_docs_to_resource_api

Type: bool

Default: false

When true, resource documentation is automatically included in the standard CKAN resource API response. This allows clients to retrieve documentation without making a separate API call.

[!IMPORTANT] Appending resource documentation to the API response can impact performance and response size.

Example:

ckanext.resource_docs.append_docs_to_resource_api = true

Example API response

With append_docs_to_resource_api = true and the default api_field_name:

{
  "id": "resource-id-123",
  "name": "my-resource.csv",
  "url": "https://example.com/data.csv",
  "format": "CSV",
  "resource_docs": {
    "documentation": "This dataset contains...",
    "fields": [
      {
        "name": "column1",
        "description": "Description of column1",
        "type": "string"
      }
    ]
  }
}

ckanext.resource_docs.api_field_name

Type: string

Default: resource_docs

Specifies the field name in the API response that will contain the resource documentation. Only applies if append_docs_to_resource_api is enabled.

[!WARNING] Ensure, that your schema doesn't use the same field name to avoid conflicts.

Example:

ckanext.resource_docs.api_field_name = documentation

With this setting, the documentation appears under "documentation" field instead of "resource_docs".


ckanext.resource_docs.show_view

Type: bool

Default: false

When true, the resource documentation is displayed in the resource view page in the CKAN web interface.

Example:

ckanext.resource_docs.show_view = true

View example:

Resource doc view example

Interface

The IResourceDocs interface allows CKAN plugins to extend the behavior of resource documentation extension.

Current methods:

  • prepopulate_resource_docs - Provide initial documentation using resource metadata.

Example implementation

import json

import ckan.plugins as p
import ckan.logic as tk

from ckanext.resource_docs.interfaces import IResourceDocs

class YourPlugin(p.SingletonPlugin):
    """Example plugin implementing IResourceDocs."""

    ...
    p.implements(IResourceDocs, inherit=True)

    def prepopulate_resource_docs(self, resource: dict[str, Any]) -> str:
        """Provide initial documentation using the DataStore Data Dictionary."""
        try:
            result = tk.get_action("datastore_info")(
                {"user": tk.current_user.name if tk.current_user else ""},
                {"id": resource["id"]}
            )
        except (tk.ValidationError, tk.ObjectNotFound):
            return ""

        return json.dumps(result["fields"])

Developer installation

To install ckanext-resource-docs for development, activate your CKAN virtualenv and do:

git clone https://github.com/DataShades/ckanext-resource-docs.git
cd ckanext-resource-docs
pip install -e .

Tests

To run the tests, do:

pytest --ckan-ini=test.ini

License

AGPL

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

ckanext_resource_docs-0.4.5.tar.gz (336.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

ckanext_resource_docs-0.4.5-py3-none-any.whl (343.6 kB view details)

Uploaded Python 3

File details

Details for the file ckanext_resource_docs-0.4.5.tar.gz.

File metadata

  • Download URL: ckanext_resource_docs-0.4.5.tar.gz
  • Upload date:
  • Size: 336.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.10.18

File hashes

Hashes for ckanext_resource_docs-0.4.5.tar.gz
Algorithm Hash digest
SHA256 ed19ea55bf5e95c23ab9f60eedbb5fb12c82c1f6a053f3cee651e355c7ed16a9
MD5 e67cf988faa0ea14d4055adaf6f67658
BLAKE2b-256 ade374602ce0f87976981933e3b75e33d5dc8783c80443fa8e7ea2290b47d292

See more details on using hashes here.

File details

Details for the file ckanext_resource_docs-0.4.5-py3-none-any.whl.

File metadata

File hashes

Hashes for ckanext_resource_docs-0.4.5-py3-none-any.whl
Algorithm Hash digest
SHA256 106a96c9cea170097a007545ffa84ca06ab0add576582200c282878012aed39d
MD5 1921e8eeade58ffca452ee89a45de8d0
BLAKE2b-256 36e3f8213199e6db4a68144d6e9e66d0fb48439956614c0aff32866c847d3d63

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page