Refactoring Metadata Edit

[geofranzi]

• Transform current view into Svelte
• Shift current continuous validation to UI
• Only talk to the backend if needed
• Create default UI components for each supported data type
• Create UI setting options to allow user-defined components to render editing & view
• UI settings global & based on schema

Wishlist for UI components

Display

Selection lists

• multi-selection list as checkboxes
• single selection list as radio
• dynamic lists (allow new entry)
• fixed selection (default - > flex default based on length?)
• fixed selection with a search on type

External Services

• DOI (enter DOI and return the title for validation)
• ROR (enter the institute and get ROR back)
• [ ] #1741

internal service:

• Link Datasets of type x

related issues:

• [ ] #393

Implementation

• Parse JSON Schema to build a form
• Add data from JSON to form
• Create default input components (date, text, textarea, number, auto-complete, ...)
  • input / Output and Settings for surrounding container (extend existing concept)
  • Complex components:
  • Mapping/Transform from/to Schema to component (from elements and attributes)
  • https://github.com/BEXIS2/Core/issues/1817
  • Settings editing:
    • Mapping rules (UI)
    • Component-specific settings
  • Example components:

    • 1741

    • Party
    • select list variations
• Fixed layout rules for the beginning (e.g., two columns per default, 1 column complex always full width, ..)

[aostrow]

Selection list

• autocomplete with single selection and fixed selection (autocomplete forced)
• autocomplete with single selection and dynamic selection (autocomplete optional, own entry allowed)