Add use cases for dataset curation status and submit for review
@ChengShi-1 已經在處理了。
開始於 2026年10月8日。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 72/100
- Issue 類型
- 功能
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
研究方向
Read the existing datasets use cases under the package's datasets domain folder (e.g. an existing Get* use case), then IDatasetsRepository and its DatasetsRepository HTTP implementation, to copy the use-case → interface → implementation pattern. Map the six endpoints from the table, export everything from the package's public entry point, and mirror existing unit tests (delegation, error propagation) plus integration tests for numeric/persistent IDs. Done means docs/useCases.md and the [Unreleased] changelog updated and build, type-check, lint, unit tests and integration tests pass.
由索引模型根據 Issue 內容生成。
描述
Overview of the feature request
Add public use cases for the existing Dataverse curation-status APIs so the SPA can support the same label selection, removal, and history functionality as JSF. Curation labels are configurable tracking values. Changing a label does not submit a dataset for review, return it to its author, or publish it.
Also, add an use case of Submit for Review for anonymous user to submit the dataset to review.
What inspired the request?
The frontend's ChangeCurationStatusMenu currently opens the not-implemented modal. Its allowed labels come from hard-coded values in DataverseInfoJSDataverseRepository.getExternalStatusesAllowed(). The frontend needs the effective labels for each dataset and reusable client methods for the real API operations.
What existing behavior do you want changed?
Expose these operations through the package's public API, following the existing use-case → repository interface → repository implementation pattern. Consumers should not need direct HTTP requests or imports from internal dist/ paths.
Any brand new behavior do you want to add to dataverse-client-javascript?
Proposed use cases (names can follow project conventions):
| Use case | Backend API |
|---|---|
GetAllowedDatasetCurationLabels |
GET /api/datasets/{id}/allowedCurationLabels |
GetDatasetCurationStatus |
GET /api/datasets/{id}/curationStatus |
GetDatasetCurationStatusHistory |
GET /api/datasets/{id}/curationStatus?includeHistory=true |
SetDatasetCurationStatus |
PUT /api/datasets/{id}/curationStatus?label={label} |
DeleteDatasetCurationStatus |
DELETE /api/datasets/{id}/curationStatus |
SubmitforReview |
POST /api/datasets/{id}/submitForReview |
Acceptance criteria
- Implement and publicly export all five use cases and their models.
- Extend
IDatasetsRepositoryandDatasetsRepository, with response mapping as needed. - Add unit tests for delegation, response normalization, history/removal records, and error propagation.
- Add integration tests for numeric and persistent IDs, query encoding, allowed-label retrieval, set/read/change/remove/history, and forbidden or invalid operations.
- Verify a status change does not change review locks or publication state.
- Document required configuration (
:AllowedCurationLabelsand effective label-set selection), publisher permissions for mutations/allowed-label reads, and configurable visibility for status reads. - Update
docs/useCases.mdand the[Unreleased]changelog; pass build, type checking, lint, and relevant tests.
This issue covers client wrappers for existing curation-status APIs. Frontend components, administrator label-set configuration APIs, submit-for-review, and return-to-author use cases can be tracked separately.
Any open or closed issues related to this feature request?
No matching curation-status issue was found. #447 concerns linked review datasets, which are separate from curation labels and their history.
References:
- 主要語言
- TypeScript
- 星號
- 20
- 分支
- 11
- 平均合併
- 4 天 9 小時
- 30 天內合併 PR
- 3
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
IQSS/dataverse-client-javascript 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
IQSS/dataverse-client-javascript#477 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 68/100
IQSS/dataverse-client-javascript#476 · 4 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 76/100
IQSS/dataverse-client-javascript#465 · 1 則留言 · 2 個 reaction ·
-
GREI Re-arch
難度 2/5 1-3 小時 新手友好度 72/100
-
Feature Request: Extend getMyDataCollectionItems search capabilities可能已有人在做 @vera 於 11 天前認領。 未關閉
難度 4/5 3-5 天 新手友好度 66/100
查看 IQSS/dataverse-client-javascript 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 82/100
Agenta-AI/agenta#7542 · 1 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
code quality security
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 90/100
-
難度 1/5 1 小時以內 新手友好度 82/100
homarr-labs/dashboard-icons#2939 ·
維護者通常 1 天內回覆