field-parser not applying the visibility configuration
维护者通常 1 天内回复
@AdamF42 已经在做这个了。
开始于 2026年10月15日。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- angular, typescript
- 领域
- frontend
调研方向
Start with src/app/submission/utils/visibility.util.ts and the section-visibility and submission-scope-type models it uses, then check whether the backend's SubmissionFormConverter.java still sends the visibility data in the old 9.2 format. Reproduce by setting a workflow visibility and readonly on dc.title in submission-forms.xml, then confirm whether the field is disabled. Done means the field is read-only in the submission form, or the cause is confirmed as backend-only and the issue is moved there.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
When a metadata field is configured to have a limited visibility in the back-end, this configuration is not being applied in the front-end.
I noticed that there were some changes to the code related to this functionality on the front-end, but no equivalent changes were made on the back-end.
In the current front-end, the main code that applies the configuration in a given field is:
https://github.com/DSpace/dspace-angular/blob/7f59f6cf99f0d1fb4b2abe46e9f24a5e1ee01a49/src/app/submission/utils/visibility.util.ts#L19-L23
and
However, the returned data from the back-end still returns in the same format as it was in 9.2 (blame is from 8 years ago).
Therefore, I'm not sure if it is a front-end bug or a back-end (maybe a missing PR?).
To Reproduce
Steps to reproduce the behavior:
- In the back-end, edit
submission-forms.xmlby adding to some field (dc.title for example) the following config:
<visibility>workflow</visibility>
<readonly>readonly</readonly>
This should make the existing field read-only (disabled) during submission.
2. Start/restart the DSpace backend.
3. Start/edit a submission.
4. The field will still be available for editing. If you try this same configuration in DSpace 9.2, the field will be disabled (works even if you use the DSpace 10.0 backend alongside the DSpace 9.2 frontend).
Expected behavior
The visibility configuration from the back-end should reflect in the forms fields.
- 主要语言
- TypeScript
- 星标
- 180
- 派生
- 577
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 95
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DSpace/dspace-angular 的其他 Issue
-
accessibility affects: 10.x affects: main bug ux
难度 2/5 1-3 小时 新手友好度 72/100
DSpace/dspace-angular#6531 · 1 条评论 ·
维护者通常 1 天内回复
-
accessibility affects: 10.x affects: main bug help wanted
难度 2/5 1-3 小时 新手友好度 66/100
DSpace/dspace-angular#6530 ·
维护者通常 1 天内回复
-
Submission Form Allows Deletion of All Repeating Item Entries可能已有人在做 @Rowan-McKereghan 于 5 天前认领。 未关闭affects: 8.x affects: 9.x bug component: submission
难度 2/5 1-3 小时 新手友好度 72/100
DSpace/dspace-angular#6511 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Visual issues with qualdrop fields可能已有人在做 @DanGastardelli 于 15 天前认领。 未关闭affects: 10.x affects: 9.x bug claimed: Acervos Digitais component: submission Difficulty: Low ux
难度 2/5 1-3 小时 新手友好度 66/100
DSpace/dspace-angular#6412 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Facet headings have incorrect clickable area to expand/collapse可能已有人在做 @jesielviana 于 12 天前认领。 未关闭accessibility affects: 10.x affects: 8.x affects: 9.x bug ux
难度 2/5 1-3 小时 新手友好度 72/100
DSpace/dspace-angular#6364 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 DSpace/dspace-angular 的全部 Issue
相似的 Issue
-
[analytics-core] getQueryParams does not decode `+` as space and truncates values containing `=`未关闭bug
难度 2/5 1-3 小时 新手友好度 82/100
amplitude/Amplitude-TypeScript#2179 · 1 条评论 ·
维护者通常 2 天内回复
-
ci good first issue severity: low
难度 2/5 1-3 小时 新手友好度 68/100
TMHSDigital/GH-Arcade#111 ·
-
AsnIntegerConverter.toASN coerces strings with +value, rounding integers outside safe-integer range未关闭
难度 2/5 1-3 小时 新手友好度 78/100
PeculiarVentures/asn1-schema#189 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100