Skip to content

Should GeographicScope be a required field? #15

@hughstimson

Description

@hughstimson

From Colin Newall:

Suggest elevating “GeographicScope” and “OrganizationName” to required. These seem straightforward to populate and I suspect these will be valuable info to report on over time so consistency would be useful. For the former, cross-referencing with the BC Geographical Names Web Service would help ensure the values are consistent.

I worry that some consulting organizations may not think in terms of geographic scope, and may not want to think in new ways. But I certainly agree it's very important context for the rest of the data. Other opinions?

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