ckan / ckan/ckanext-scheming

Feature request: retain extra fields

Open
#14 7 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
102
Forks
182
PR merge metrics
No merged PRs in 30d

Description

Not sure whether this is a bug or a feature, but it seems that enabling ckanext-scheming with a custom schema will, on first saving a dataset with the new schema, delete any existing "extra" fields. Even to only retain the existing extra fields to safely migrate data would be helpful - this could be achieved if config settings would toggle the display of existing extra fields and/or form fields.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the first dataset save with ckanext-scheming enabled and a custom schema, then trace where existing "extra" fields are removed. Done means existing extra fields are retained during migration, with any configuration for displaying them or their form fields defined and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.