Skip to content

alternate_building_names should have own file #68

@lkmorlan

Description

@lkmorlan

There should be a separate file to store the data now in column alternate_building_names in Buildings.csv. The columns of this new file should be (building_id, alternative_name) and these should together form the primary key. Once this is done, alternate_building_names should be removed from Buildings.csv.

This creates a better relational structure and keeps the data in Buildings.csv objective.

Another possibility would be to have primary key (building_id, name) and another column to define the status of the name, such as colloquial or archaic.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions