Smarter automatic deduplication

未关闭
#31 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
data

调研方向

This is a design decision, not a ready edit. Start by reading the automatic deduplication work referenced in #25 and how DP+ handles duplicates before the resource is pushed to the Datastore. The issue offers three options (stop the job with an error, replace the resource file with the deduplicated CSV, or use qsv dedup --dupes-output to push _dupes and _dedupped resources), and no option is chosen. Done means a maintainer agrees on one approach first, then it is implemented.

由索引模型根据 Issue 内容生成。

描述

enhancement

Automatic deduplication works well (#25), however, when duplicates are found and removed, the datastore table and the resource file are no longer in sync.

Smarter dedup can be handled three ways. When dupes are found:

  1. Stop the DP+ job and show the dupe error in the Datastore tab.
  2. Replace the resource file with the dedupped CSV.
  3. Take advantage of qsv dedup's --dupes-output option and create two new resources - RESOURCENAME_dupes.csv and RESOURCENAME_dedupped.csv which are pushed to the Datastore. The original resource with dupes is NOT pushed. The Data Publisher can then just use the CKAN interface to manage which resource to keep (e.g. delete the original and the _dupes resources; rename the _dedupped resource, removing the _dedupped suffix.)
主要语言
Python
星标
47
派生
33
平均合并
2 小时 28 分钟
30 天内合并 PR
10

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

dathere/datapusher-plus 的其他 Issue

查看 dathere/datapusher-plus 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。