More configuration options

[arildm]

Step one was to provide a minimal, very basic set of options.

Step two is to have the configuration options generated from the actual schema that Sparv accepts.

[arildm]

These are some needs that were apparent from user testing:

• Recognition of older Swedish
• CSV output (done in https://github.com/spraakbanken/mink-backend/commit/299e74a58bf2a200083a9bd7cd610e1a5a14fa92)
• Specify if source texts are already tokenized
• CONLL input (Sparv does not support this)
• PDF input (Sparv does not support this) (done in https://github.com/spraakbanken/mink-backend/commit/182e1093cd9526b7acf67873a0e3fd85e1123bee)
• Entire export as single XML (Sparv does not support this?)
• NER

[arildm]

The config-schema branch now has a config form that is automatically generated from Sparv's JSON schema. Discussed it with Martin today and we probably need to:

• [ ] Add item definitions
• [ ] Add translated field names/descriptions in frontend
• [ ] Divide the huge form into groups like "Metadata", "Import", "Annotator settings"...
  • [ ] Research what customization options are offered by the form library (React JSON Schema Form, RJSF) and their "UI Schema"
• [ ] Fix markup/styling so the add/remove buttons are visible
• [ ] Better rendering of fields that allow translatable strings (like metadata.description)
  • [ ] And other objects with arbitrary keys
• [ ] Check that build size doesn't explode due to including the React libs