Issues with creating new item

[drengur]

https://github.com/user-attachments/assets/2c13da75-b01e-4db5-83b3-18ea64ef19d7
When creating a new item, the state of the dropdown box containing the type of resource seems to vanish when changing the type of resource. This has been bothering me for some time, and I can not figure out why this happens. There is no error in the logs. But I have observed that If I click the collection dropdown before I click the resource type dropdown, I can update the type of resource. I hope I am not being to fuzzy, but to make things clearer I have attached a video of the procedure I am trying to describe here. I have only one collection in this community.

[kosarko]

@drengur hi, and that happens on something that's built on a ~current clarin-v7 (FE+BE) branch (or one of tha 2026.* tagged releases)? Also when you open chrome dev tools (F12), do you see any errors (either in the console directly, or in the network tab as 4xx/5xx status codes)?

[drengur]

I pulled these two images yesterday:
"Image": "ufal/dspace-angular:dspace-7_x",
"Image": "ufal/dspace:dspace-7_x",

In the browser network windows, there is a "PATCH" call to the backend with a status 200 "OK" response (https://repotest.clarin.is/server/api/submission/workspaceitems/619).
The console window is empty. There are no other messages.

[kosarko]

@drengur I have a fix prepared in #157, could you try deploying https://hub.docker.com/layers/ufal/dspace-angular/worktree-1377-item-type-dropdown/images/sha256-1777ee7bdea313a6d4e6595824f8cb2b5e2f094ab46b427bbbae0ddf14ba6ef0 as the FE image and check if it fixes the issue?

Some notes (based on AI analysis)

• The value is persisted: the PATCH /server/api/submission/workspaceitems/{id}
  returns 200 and the backend keeps the value. This is a display / change-detection
  bug, not data loss.
• No console errors, no 4xx/5xx.
• Workaround: clicking the Collection dropdown before touching the type
  dropdown makes the change stick. (The extra interaction forces an Angular
  change-detection cycle that re-renders the dropdown.)

It only reproduces under backend latency. The bug is a race condition widened by slow backend round-trips:

• The reporter runs against a remote backend
• On a fast/local backend the same reload finishes in <100ms, so the dropdown
  re-populates imperceptibly and the bug is invisible. Selecting/re-selecting the
  type "just works" locally, even with rapid repeated changes.

When dc.type changes, the Describe section reloads its configuration (type-bind:
different types show/hide different fields) and re-renders. On re-init,
DsDynamicScrollableDropdownComponent runs:

ngOnInit → loadOptions(true) → setCurrentValue(model.value, true)

which derives the displayed text via getInitValueFromModel().map(v => v.display).
If the reloaded dc.type value comes back as a FormFieldMetadataValueObject
carrying only authority/value with an empty display, the shown text is
empty even though the underlying value is intact. The Collection-dropdown
workaround forces a later CD cycle that re-evaluates currentValue and restores
the text — consistent with a display-only defect.

Regarding the mentions of backend response speed. Would it be possible to share some stats?

sudo grep -E "(GET|POST|PUT|DELETE|PATCH) /repository/server/api" /var/log/nginx/access.log | awk '$9 >= 200 && $9<300 {print}' | rev | cut -d" " -f2 | rev | awk '{a[NR]=$NF; sum+=$NF} END {n=NR; asort(a); print "n:", n, "\nMean:", sum/n, "\n50th:", a[int(n*0.5)], "\n95th:", a[int(n*0.95)], "\n99th:", a[int(n*0.99)], "\n99.999th", a[int(n*0.99999)], "\nmax:", a[n]}'
n: 3645911
Mean: 0.267242
50th: 0.003
95th: 0.146
99th: 0.499
99.999th 5335.061
max: 12340.026

Those are the numbers for the current month. I'm not sure you can reuse the oneliner as is so some comments - the first grep filters for our backend path, then the awk leaves only 2xx rows (in our logs $status can be obtained as the 9th field), then it gets $upstream_response_time (which is 2nd field from the end of the line in our log format) and then it computes the stats. Maybe this won't show anything, just curious...

[drengur]

Thank you. I am on a three day vacation. I will be back on monday to test the fix.