Ticket #1069 (assigned enhancement)

Opened 3 years ago

Last modified 23 months ago

Stub datasets (request for datasets)

Reported by: rgrp Owned by: tobes
Priority: awaiting triage Milestone:
Component: ckan Keywords:
Cc: tobes Repository: ckan
Theme: none


Idea is to have stubs for datasets that someone wants but don't yet exist (or haven't been discovered) in the way one has stub pages on a wiki.

We could do this within the existing model by a slight 'abuse' - create a dataset and mark it with a special tag e.g. todo.does-not-yet-exist or similar ...

(Just as we have datasets listed that exist but aren't available ...)

Alternative would be to have a request for datasets subsystem.

I prefer the stub dataset model because it's simpler, provides a simple workflow (as a dataset is found or comes into existence), and the package page provides a natural space in which to accumulate information about what is wanted and what exists.


  • Agree a new dedicated tag. e.g. todo.does-not-exist

Change History

comment:1 Changed 3 years ago by thejimmyg

  • Milestone changed from ckan-v1.5 to ckan-v1.4-sprint-5

This is what the new "Ideas" section in the ckanext-community extension is for. Marking as duplicate of #941, can we have discussion there please.

comment:2 Changed 3 years ago by rgrp

  • Milestone changed from ckan-v1.4-sprint-5 to ckan-v1.5

Mistakenly assigned to this sprint.

comment:3 Changed 3 years ago by thejimmyg

  • Milestone changed from ckan-v1.5 to ckan-backlog

Yes, and this will be more important in thedatahub.org

comment:4 Changed 3 years ago by thejimmyg

  • Milestone ckan-backlog deleted

comment:5 Changed 23 months ago by icmurray

  • Cc tobes added
  • Owner changed from rgrp to tobes
  • Status changed from new to assigned

Assigned to @tobes as he's looking at publication workflows.

Note: See TracTickets for help on using tickets.