Skip to content

bug: Non-traditional date/time format #249

@JMCulhane

Description

@JMCulhane

Bug Report

v0.9.0

Current behavior:

Currently, the CLI is not configured to handle data sets with non-traditional date formats, such as separate parsing separate columns for Date and Time. In my testing, I noticed that the hour column from the ROK election data sheet was being parsed as 'identifier', as opposed to one of the time semantics.

Expected behavior:

The CLI should be able to parse and concatenate date and time columns when they are separate.

Steps to reproduce:

Using this data sheet: https://drive.google.com/file/d/17xfpGmnJsCWZeFyuNKR9zQPZm--zIa0D/view?usp=drive_link, import the set. Be sure to modify the import with comma separators in the CLI, as the dataset is a bit finnicky.

Notice below that the hours do no get concatenated into the timestamp:

Image

Subtask:

  • Create military time converter

Sub-issues

Metadata

Metadata

Assignees

Labels

in-progressIssue is currently being worked on by a developer.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions