-
Notifications
You must be signed in to change notification settings - Fork 33
Description
Expected Behaviour
Given the current form:
- Users see the entries from the dataset schema that are common across raw/derived dataset and we enforce users to provide the mandatory fields. ( here user specifies if it's a raw or derived)
- Check differences in API V3 and V4 in the DTOs of raw and derived datasets, add compatibility when necessary. Additional fields appear in the questionnaire if any those are needed for any dataset type.
- Ask user if they want to provide the schema for the scientific metadata. Must be a reachable URL.
- Form expands with the schema fields.
- Upon save a POST request is sent to the backend
- Message "Dataset creation successful/failed" and redirect to it
Current Behaviour
Details
There are similar forms in development by Martin on Published Data and from David on OpenEM Ingestor. We should reuse the technology (jsonforms) and agree on the same style
Sub-issues
Metadata
Metadata
Assignees
Labels
No labels