Files
aimsight-libredesk/snippets/textes/my-exported-csv-file-does-not-contain-a-timestamp-what-should-i-do.md
T
maximeandClaude Opus 5.5 10ed887417 Noms plus clairs : snippets/, scripts de test numérotés, verifier_ollama.py
- base_connaissances/ → snippets/ (corpus/ → textes/, instructions.md → consignes_redaction.md, decoupage.py → fichiers.py, importer.py → envoyer.py) ; python3 -m snippets.envoyer.
- instance-de-test/ : 1_demarrer.sh, 2_creer_boite_et_cle.py, 3_brancher_ia.py, 4_essayer_brouillons.py, voir_empreintes.sh, connexion_admin.py.
- ollama/verifier.py → ollama/verifier_ollama.py ; tests, tâches VS Code et docs alignés.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 10:27:06 +01:00

12 lines
568 B
Markdown

# My exported CSV file does not contain a timestamp. What should I do?
Time information is required for most external data-processing workflows.
If the selected CSV export does not contain a timestamp, check the export type and
configuration being used.
Where required, the export configuration can be adapted so that each measurement contains an
explicit timestamp suitable for external processing.
For data integration, the timestamp convention should always be defined explicitly rather than
inferred from the file creation time.
Source : AIMsight FAQ, rév. 1.5