Closed ryanfb closed 7 years ago
This would give e.g. https://pleiades.stoa.org/places/109242/parisii for a name or https://pleiades.stoa.org/places/109242/undetermined for a location, instead of just the URI from the associated place https://pleiades.stoa.org/places/109242.
We would need to normalize this inside our comparison functions because we store the associated place geo against the place URI.
Related to #13 - what do we consider a duplicate here?
Following from Skype discussion, we decided to keep names the same (just place), and normalize location URIs down to the associated place as well.
This would give e.g. https://pleiades.stoa.org/places/109242/parisii for a name or https://pleiades.stoa.org/places/109242/undetermined for a location, instead of just the URI from the associated place https://pleiades.stoa.org/places/109242.
We would need to normalize this inside our comparison functions because we store the associated place geo against the place URI.
Related to #13 - what do we consider a duplicate here?