Feedback by Paul Remmler

I had a meeting with Paul at 03.03.2026 with the current main version of the data source management. I will list his feedback here. These should be transformed into more fine grained issues in jira.

• copy-functionality where possible (for ingests, parser, quality control settings)
• overview table of parser: records per page default 20
• delete buttons also in the overview tables (with additional dialog to confirm)
• possibility to filter (we haven't defined which filters, maybe take a look at the brainaio thing-maangement or suggest one)
• Creation/Edit Form Parser:
  • it would be nice to have a suggested name based on the inputs made (a generation rule was not defined)
  • headlines/footlines to exclude the 0-based text should be removed as you put in numbers there and not the line numbers (currently)
  • button to add new timestamp columns should be below the new inserted row
  • timestamp format should have a reference link to the documentation
  • column delimiter should also contain examples for the most common one: comma, semicolon, tab and a reference to the timeio wiki
  • in the parser selection:
    • a link to the parser would be nice and maybe some additional information like delimiter or tmestamp column with format directly in the selection
• Detail pages:
  • UUID should be copy-to-clipboard
• Ingest SFTP: add Link to minio storage
• Ingest Overview:
  • Cards with links to respective overviews for SFTP, MQTT, EXTERNAL SFTP, EXTERNAL API
  • EXTERNAL API should then contain Cards for the several other types as Cards as well
• Search function over all ingests, it should be searching for name and description
  • that's a little bit complex as the api must provide an endpoint and must search for all (should there be one endpoint or should all ingest provide a search and the frontend queries all endpoints?)
• Parser discussion:
  • It would be nice to have one parser that could be used in several projects, as the same devices are used so the same parser should be needed
  • My/our ideas on that:
    • a parser should belong to more than one permission group (like a device in sms could belong to several groups)
    • there are parsers that don't belong to a specific permission group, but could be selected
      • that could be achieved by having an extra table like standard_parser_csv and an extra endpoint to get those parser. These could be either only be entered via database access or we have a fancy form for super_user
• more description everywhere
• help text where possible
• Links to WIKI, Repo, SMS, (API Definition, but I would leave that as we don't allow to use the api directly)