Frontend Issue — Enhanced Keywords Input & Selection
🎯  Goal
Improve the Keywords input for samples in SEPIA to:
- 
Reduce invalid, controversial, or “nonsense” entries.
 - 
Prefill suggested keywords based on sample type schemas in JSON.
 - 
Allow existing vocabularies (BattINFO, voc4cat, terminology service) for selection.
 - 
Provide two inputs:
- Existing terms from vocabulary
 - Free-entry field for new terms (with validation/curation suggestions)
 
 
🧩  Implementation Details
UI Behavior
- 
1. Existing Terms Input - 
Dropdown / autocomplete showing terms from selected vocabularies.  - 
Search and filter across multiple vocabularies dynamically as user types.  - 
Allow choosing the most domain-appropriate term (e.g., “Temperature” in astrophysics vs catalysis).  
 - 
 - 
2. Free Entry Input - 
Allow users to enter new keywords not in vocabularies.  - 
Implement soft validation or warnings for potentially ambiguous terms.  
 - 
 - 
3. Prefill Suggestions - 
Based on sample type JSON schema, suggest relevant keywords automatically.  - 
User can select or deselect these suggestions.  
 - 
 - 
4. Curation / Validation - 
Optional: mark controversial or multi-definition terms with a warning.  - 
Provide tooltip or guidance for proper selection.  
 - 
 
🧪  Testing
- 
Keywords dropdown shows correct terms from vocabularies.  - 
Autocomplete updates dynamically as user types.  - 
Prefilled suggestions from sample type schema appear correctly.  - 
Free entry input allows valid entries but flags suspicious terms.  - 
Selected terms are submitted correctly with sample creation/update.  
🏷️  Labels
frontend feature keywords sample priority::medium