DP+ 3.0 tracking issue

未关闭
  • 哪里不对？
#259 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
8/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
bootstrap, postgresql, python
领域
documentation

调研方向

This is a tracking issue for the DP+ 3.0 release rather than a single task, and its unchecked item (incorporating the TX Form Pages: Registration, Upload and Review formpages) is design-heavy. Start by reading the linked PRs #263, #264 and #307 to see how the work has landed, and check the scheming form snippets in the repository. Done would mean the remaining unchecked items are closed or split into their own issues.

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

描述

DP+ 3.0 will make the Data Resource Upload Flow (DRUF) that was developed for the Texas Water Data Hub generally available.

The DRUF is interactive FAIRification, featuring:

  • ckanext-scheming 3.0 powered Dataset Form Pages with a standard Upload page in the beginning, and a Review page at the end.
  • metadata formulas - Excel like formula DSL using jinja2 that can calculate/suggest metadata. They can either be pre-calculated and assigned automatically or offered as suggestions.
  • Extensible formula helper library - since the formulas are written in jinja2, additional helpers can be easily added. The formula helpers will prioritize precalculating DCAT-US 3 recommended optional properties that are otherwise too hard to calculate manually (#218)
  • suggestion UX/UI - a Suggestion UI using Bootstrap popovers that show the Suggestion and the Formula.
  • apply scheming 3.0 changes
  • reorganize project for maintainability https://github.com/dathere/datapusher-plus/pull/264
    (DO THIS FIRST, BEFORE ITEMS BELOW)
  • https://github.com/dathere/datapusher-plus/pull/263 — merged 2025-11-23 (69f5481); truncate in its own txn so the AccessExclusive lock is held for the shortest possible window, eliminating UI hangs on large COPY-into-datastore jobs.
  • incorporate TX Form Pages implementation - specifically, the Registration Formpage and the Upload formpage in the beginning, and the Review Formpage at the end.
  • incorporate AI-powered suggestions for Description and Data Dictionary using qsv describegpt — backend in #301 (fdc3714), scheming UI in #302 (ad28ebc), qsv-flag + envelope-shape fixes from LM Studio E2E in #303, and Vitest + jsdom unit suite in #304 (which also caught a production bug where the polling JS was reading STATUS from the wrong path and would never have terminated). Opt-in via ckanext.datapusher_plus.enable_ai_suggestions (off by default; needs an OpenAI-compatible endpoint configured in qsv's describegpt prompt-file). Per-field opt-in via ai_suggestion: true on the scheming field config; AI buttons appear next to opted-in fields on markdown / text / select form snippets, polling JS reads suggestions from package["dpp_suggestions"]["ai_suggestions"] and applies on click.
  • extend qsv describegpt so that it can use a controlled vocabulary for suggested tags. The controlled vocabulary will be configurable and point to the specified CKAN resource with the following columns tag, description, AI guidance. AI guidance will be customizable instructions when/how to use the associated tag.
  • leverage qsv's delimiter inferencing (see #256) — done in efb254f; format_converter.py:319-340 now sniffs and normalizes non-comma CSVs
  • #261
  • #262
  • #265 — stash + restore Data Dictionary across DP+ job failures, landed in #307 (59e08d7). Analysis stage writes a small per-resource JSON snapshot to disk before deleting the existing datastore; _rollback_database reads it back on failure and re-creates the datastore with the original info dicts (and proper type derived from type_override) and zero rows. A retry branch in AnalysisStage._parse_stats re-loads the stash when no live datastore exists, so the dictionary survives even when the failure happened outside the database transaction. Stash mtime is surfaced in restore logs so operators can spot stale-restore vs. genuine retry. New knob ckanext.datapusher_plus.dictionary_stash_dir (defaults to <tempdir>/dpp_dict_stash).
主要语言
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 摘要。