Skip to content

pamidb_to_json.py: line tabulation kill? #25

Open

Description

@bturkus

Hi,
I've noticed that, from time to time, we've been accidentally adding (and not noticing) extra lines being added to database fields. These pose a problem because, when exported in merge files and transformed into JSON, they end up as weird new line characters that fail validation.

So this in a mer:
screen shot 2018-02-23 at 9 00 50 am
Ends up as this in JSON:
screen shot 2018-02-21 at 9 53 17 am

We can certainly try to impose more order in the a database, but I see this being a recurring problem, and if we could add a kill mechanism of some sort (without losing information), that'd be wonderful.
Let me know what you think...
Thanks,
Ben

Activity

  1. nkrabben commented on Feb 23, 2018

    @nkrabben
    Collaborator

    This is a wonderful feature request. Let's queue up a ticket.

  2. bturkus commented on Mar 19, 2018

    @bturkus
    CollaboratorAuthor

    False prophet ben here, maybe make a list of kill characters and wack the data frame with a replace function.

  3. nkrabben commented on Jan 13, 2021

    @nkrabben
    Collaborator

    Do you have a list of kill characters? and what should they be replaced with? ""?

  4. bturkus commented on Feb 3, 2021

    @bturkus
    CollaboratorAuthor

    this one is worth keeping open I think. I'll work on a list fo characters, but I believe this /u000b is the big offender

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions