Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autocomplete: custom options #187

Open
jusa3 opened this issue Jan 10, 2025 · 1 comment
Open

Autocomplete: custom options #187

jusa3 opened this issue Jan 10, 2025 · 1 comment
Labels
enhancement New feature or request question Further information is requested

Comments

@jusa3
Copy link
Collaborator

jusa3 commented Jan 10, 2025

To discuss in our weekly

Provide a set of custom options that should be selectable, e.g. 'Other', 'Not applicable' and 'Unknown'.

Use case: data entry form where users should select a concept from an ontology or, if no option is suitable, state the reason why this property cannot be filled in, i.e. explain the missing (to avoid storing an empty value (i.e. no information) and we do not know why no information is provided).

See #14 (comment)

@jusa3 jusa3 added enhancement New feature or request question Further information is requested labels Jan 10, 2025
@jusa3
Copy link
Collaborator Author

jusa3 commented Jan 14, 2025

This use case is needed when autocomplete is used in a form to define keywords, for example. The purpose of a reusable widget is to be used in different kinds of use cases, especially for linking semantic concepts; this new feature wouldn't make it more complex, but it would make it more widely applicable IMO.

I see the following realisation (based on #14 (comment)):
Creating two checkboxes for "not applicable" (if key terms are not allowed/needed) and "unknown" (if the user doesn't know what to enter). The option "others" (if no matching key term is found in the autocomplete) could be displayed within the autocomplete drop down if nothing else matches.

In a first implementation, the input property will be the IRIs of the three concepts, provided they are represented in the underlying terminology service database (the selected API). In a second implementation (when the TS4NFDI Gateway is available and value sets are implemented), a value set can be created and applied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant