Datastore enhancements
- Dominant language
- No language data
- Stars
- 39
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Some user stories for enhancements to the datastore to make it more useful in production.
As a developer
I want to be able to access all sheets from an XLS via the API
So that I don’t miss out and get only metadata (*)
As a developer
I don’t want to use a UUID as the tablename
So that I can understand what my API calls are doing
As a developer
I want a page per resource that describes the schema for the datastore
So that I know what I can do with it
As a developer
I want a page per resource with a form that allows me to play with the API
So that I can see what it can do and build URLs for me.
As a sysadmin
I want to get statistics on usage of the API
So that I can manage my system more effectively
(*) Most spreadsheets on our system have extra metadata in the first sheet of the spreadsheet, and data on the following sheets.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by checking the main CKAN repository Discussions, since this ideas repository is deprecated, and split the five datastore and API requests into scoped work items before implementation. Done criteria would need to be defined for each request.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, database, documentation, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100