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
{{ message }}
This repository has been archived by the owner on Feb 14, 2020. It is now read-only.
Currently, we record the owner of a metadata entry in Janus using a free text field called coin:institution_id. This field contains a (human readable) reference to our CRM (for example, UNIVEGHEL refers to the "University of Veghel" organisation in CRM).
However, a new CRM has recently been deployed, which uses uuid-like identifiers (41640424-a615-f411-80e0-006056956c1a) rather than human-readable ids. To support entering these in Janus, I propose the following:
Currently, we record the owner of a metadata entry in Janus using a free text field called coin:institution_id. This field contains a (human readable) reference to our CRM (for example, UNIVEGHEL refers to the "University of Veghel" organisation in CRM).
However, a new CRM has recently been deployed, which uses uuid-like identifiers (41640424-a615-f411-80e0-006056956c1a) rather than human-readable ids. To support entering these in Janus, I propose the following:
lookup
, which works like aselect
, but displays both the entered key and a lookup value from a predefined list. The configuration for this metadata type could look like this (ref: https://github.com/janus-ssp/janus/blob/develop/app/config-dist/config_janus_core.yml):or a fancier search box (like select2) could be used.
The text was updated successfully, but these errors were encountered: