Allow importing to metadata columns
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Is your feature request related to a problem? Please describe.
When importing from another software (AppFlowy in my case), I would like to be able to use the pre-existing metadata. In this instance, it was the row created at column, but I can see some software also having the edited time, or user (something I could also manually add). I think it would be valuable to surface this during import, rather than having a duplicated created time to deal with (a meta and non-meta column).
Describe the solution you'd like
ID is a metadata column that is selectable when choosing an existing column to use during import. I'd like to see the other columns added to this list.
Describe alternatives you've considered
Having a manually created column, not ideal as it causes data inconsistency.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the import flow and the existing ID-column selection, then identify how metadata columns are represented; done means created time and other available metadata columns can be selected during import and retain their imported values without duplicate columns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100