Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

How to handle empty fields #240

Closed
Closed
@gbinal

Description

@gbinal

A question for folks: An issue that's come up a good bit as we begin harvesting agency public data listings is whether to dictate how to handle empty fields. Take for example, the webservice field. There is of course the scenario where it's populated:

image

But there are plenty of other times when it's convenient for the field to still be in the record even when it's unpopulated. So far, I've seen this happen two ways:

  1. with a null value:
    image

  2. or with empty quotation marks:
    image

Should one or either of these be acceptable from a validation and harvesting perspective?

@konklone, @benbalter, @waldoj, @kinlane, @philipashlock, @dwcaraway, @kvuppala, @FuhuXia - can you weigh in?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions