Univention Bugzilla – Bug 56754
CSV Import für Schulen vereinfachen
Last modified: 2023-10-23 08:53:59 CEST
Es wäre schön, wenn der Benutzerimport verbessert würde, damit neue Schulen schnell ongeboarded werden können. Hier ein paar Anforderungen: - Die allerwenigsten Anwender wissen, was eine CSV UTF 8 Codierung ist. Die deutsche Excel-Version bietet keine Möglichkeit, eine CSV-Datei in UTF 8 zu erzeugen. Alternativen wie der Editor (nach Erzeugung einer txt als Alternative) oder Libre Office Calc sind unbekannt und damit eine hohe Hürde. - Das Importformat ist zu streng. -- Die genaue Zeichenkette der Überschriften muss eingehalten werden -- Leerzeichen in Spaltenüberschriften führen zu einem Importfehler -- Umlaute am Ende der Zeile eine Datensatzes führen zu einem Fehler -- Klammern führen zu einem Importfehler -- Sicher gibt es noch weitere Sonderzeichen und Zeichenketten, die zu Fehlern führen - Die Fehlermeldungen zum Import sind kryptisch: Englisch, IT-Slang, formatiert wie Code. Sie helfen deshalb nur selten und werden direkt weggeklickt. - Die Logfiles des Imports sind CSV-Dateien (nicht gut zu verarbeiten mit Excel) und werden nach einer bestimmten Zeit gelöscht, es gibt keine Hinweis die Logfiles zu downloaden – als Sicherheit.
Auto-translated to english ------------------------------------------------- It would be nice to improve the user import so that new schools can be onboarded quickly. Here are a few requirements: - Very few users know what a CSV UTF 8 encoding is. The German Excel version does not offer the possibility to create a CSV file in UTF 8. Alternatives like the editor (after generating a txt as an alternative) or Libre Office Calc are unknown and therefore a high hurdle. - The import format is too strict. -- The exact character string of the headings must be respected -- Blanks in column headings lead to an import error -- Umlauts at the end of the line of a record lead to an error -- brackets lead to an import error -- Surely there are more special characters and strings that lead to errors - The import error messages are cryptic: English, IT slang, formatted like code. Therefore they rarely help and are clicked away directly. - The logfiles of the import are CSV files (not good to process with Excel) and are deleted after a certain time, there is no hint to download the logfiles - as security.
(In reply to Daniel Tröder from comment #2) > - Very few users know what a CSV UTF 8 encoding is. The German Excel version > does not offer the possibility to create a CSV file in UTF 8. The UCS@school import is not meant to be used manually. Its use case is the consumption of automated exports from upstream systems. There was once a user-oriented import UMC module. It had features like reorderable columns etc.: https://docs.software-univention.de/ucsschool-handbuch-4.3.html#school:setup:umc:csvimport It was removed with UCS@school version 4.4 because of very few customers using it and high maintenance costs. Its only real value was for testers (not actual customers) to be able to quickly execute an import. If that use case is the reason for this issue, then I suggest to instead write a very good tutorial on how to do this with the current import. > Alternatives > like the editor (after generating a txt as an alternative) or Libre Office > Calc are unknown and therefore a high hurdle. Installing an office suite on a desktop OS should be no hurdle for somebody who wants to operate a UCS@school installation. That person is expected to edit JSON files in a terminal editor in an SSH session. The audience of the UCS@school import is professional system operators. If that should be changed, we should rethink more than just the import file format. > - The import format is too strict. > -- The exact character string of the headings must be respected Strict formats lead to fewer errors. > -- Blanks in column headings lead to an import error > -- Umlauts at the end of the line of a record lead to an error > -- brackets lead to an import error > -- Surely there are more special characters and strings that lead to errors All of those statements are only true when a bad CSV format is chosen. Using the format described in the documentation (enclosing each cell with quotation marks) will prevent all those problems. > - The import error messages are cryptic: English, IT slang, formatted like > code. Therefore they rarely help and are clicked away directly. The error messages are directed towards system operators. What audience are you referring to? > - The logfiles of the import are CSV files (not good to process with Excel) > and are deleted after a certain time, there is no hint to download the > logfiles - as security. With this comment now it's clear we're talking about the UMC import module. I have changed the component. The CSVs are not logs, but meant for statistics and result analysis. The CSVs are never deleted. The actual logfiles are rotated and thus deleted after a while. That is a privacy protection and disk-full protection requirement.