whosonfirst / whosonfirst-www-boundaryissues

Boundary Issues is a web-application for editing Who's On First data.
BSD 3-Clause "New" or "Revised" License
8 stars 0 forks source link

When changing a record's wof:name, require that name value be stored as an alt name #233

Open stepps00 opened 7 years ago

stepps00 commented 7 years ago

In our lifecycle rules document, we've stated that when a change to a record's wof:name occurs, that name value should always be stored as a name variant. If that name is not stored as a name variant, that record should be superseded into a new record (for example, if the wof:name was a complete error, but the record still represented a place IRL).

The logic to store this name should look something like:

Examples: If San Francisco changed names to Oakland, and Oakland wasn't in the alt names before, and the area also changed size, then a new record is needed.

If San Francisco changed default names to Yeurba Beuna , and that was in the list of name variants, and we preserve San Francisco in the name variants, then we "edit in place".

dphiffer commented 7 years ago

This all makes sense, thanks @stepps00 for fleshing out those rules.

Related: #140 #152 #180