ckan / ckan/ideas

Datapusher enhancements

Open
#124 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
39
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Some user stories for datapusher that might be useful to have

As a system administrator
I want clarification on where I see the datapusher status
So that I am not in the dark about failures

As a system administrator
I want datapusher to be even easier to deploy
So that I don’t have to change config in .py files.

As a developer
I want datapusher to better handle ‘errors’
So that it doesn’t crash with extra header rows

As a user
I want to see a status page showing if/why the datapusher failed
So that I can fix my data and try again

As a developer
I want datapusher to handle all sheets in an XLS
So that I don’t miss out on data

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by separating the issue's five user stories: status visibility, deployment configuration, extra header-row errors, a failure status page, and handling all XLS sheets. No files, tests, entry points, or acceptance criteria are mentioned; this is ready only after each story has a defined scope and a concrete way to verify completion.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.