You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to serialize vocabularies, for example in autocomplete dropdowns (deposit form, custom fields, etc.), they must accept the application/vnd.inveniordm.v1+json header. These response headers are configured in the resource config, for example, here.
This will serialize the record (i.e. vocabulary) including some key/value representations required by the UI. These is widely used across InvenioRDM. For example, the AutocompleteDropdown custom widget.
Contrib vocabularies on the other hand, are created using the RecordFactory, whose config does not include this response header. This is however configurable by the resource_cls_attrs parameter, see here.
Tasks
Configure the contrib resources config to accept the UI response header. One way of overwritting this can be seen in the names vocabulary.
Evaluate if the contrib vocabularies are serializable with the generic VocabularyL10NItemSchema. This means, if the correct key-values will exist. If not, a per-vocabulary schema has to be implemented.
The text was updated successfully, but these errors were encountered:
Case
In order to serialize vocabularies, for example in autocomplete dropdowns (deposit form, custom fields, etc.), they must accept the
application/vnd.inveniordm.v1+json
header. These response headers are configured in the resource config, for example, here.This will serialize the record (i.e. vocabulary) including some key/value representations required by the UI. These is widely used across InvenioRDM. For example, the AutocompleteDropdown custom widget.
Contrib vocabularies on the other hand, are created using the RecordFactory, whose config does not include this response header. This is however configurable by the
resource_cls_attrs
parameter, see here.Tasks
The text was updated successfully, but these errors were encountered: