Metadata Edit: Modification of the metadata form based on the configuration and system functions #2386
Description
Wishlist for UI components
Display
Lists (single-entry arrays)
- as a list
- comma-separated
- (now with numbering?)
Lists (compound-entry arrays)
- dynamic? 1-2-3-4 entries?
- persons (with / without middle name, with / without ORCID, with / without org, ...)
Edit
Selection lists
- multi-selection list as checkboxes
- single selection list as radio buttons
- dynamic lists (allow new entry)
- fixed selection (default - > flex default based on length?)
- fixed selection with a search on type
- allow to set/define default values
Date fields
- start/end date check ( or date range)
- special date format (only hours, ...)
Text fields
- allow default values
- ...
Map (view + edit)
External Services
- DOI (enter DOI and return the title for validation)
- ROR (enter the institute and get ROR back)
- DDM: Integration of Terminology Service Suite #1741
internal service:
- Link Datasets of type x
related issues:
Configuration
Implementation
- Metadata edit: Parse JSON schema to build a form #2007
- Metadata edit: Add data from JSON to form #2008
- Metadata edit: Create default input components (date, text, textarea, number, auto-complete, ...) #2009
- input / Output and Settings for surrounding container (extend existing concept)
- Metadata edit: Complex components #2010
- Mapping/Transform from/to Schema to component (from elements and attributes)
- DDM: Concept for settings/modes (per mode, general) -> JSON-Structure #1817
- Settings editing:
- Mapping rules (UI)
- Component-specific settings
- Example components:
- DDM: Integration of Terminology Service Suite #1741
- Party
- select list variations
- Fixed layout rules for the beginning (e.g., two columns per default, 1 column complex always full width, ..)
Sub-issues
Metadata
Metadata
Assignees
Labels
No labels