Closed mjtecka closed 5 months ago
To explain what's happening in more detail. Currently we have dc.subject
with a vocabulary
https://github.com/dataquest-dev/DSpace/blob/5968c7b705b51999c418fab35509eea5999e3288/dspace/config/submission-forms.xml#L271
;
it will split them, e.g. key1;key2
will become key1
, key2
theo
for example and a list with suggestions should appear); these seem to be saved as expeted too[x] the only issue seems to be the current setup; where the behavior should be
The vocabulary element has an optional boolean attribute closed that can be used to force input only with the Javascript of controlled-vocabulary add-on. The default behaviour (i.e. without this attribute) is as set closed="false". This allow the user also to enter the value in free way.
It lets you add a custom keyword, but eventually this is not saved. So it looks like closed="false"
but behaves like closed="true"
(ukrepo)
Subject Keywords do not work when creating new Items
1) there is just one row in the interface, I am not sure if I can input more keywords and how to separate them
2) if I Edit record that was not yet Deposited, previously filled Subject Keywords are gone
3) I cant find Subject Keywords in metadata after depositing the item There is nothing in dc.subject, or anywhere else.
(side note: I can add dc.subject manually in Edit Item -> Metadata and it works - keywords are displayed with the record and in search interface)
-> Subject Keywords should work (=should be stored in metadata record) & allow input of multiple keywords