Closed tsujigiri closed 13 years ago
changing an instruments location != changing a locations coordinates
changing an instruments location == adding a new location and changing the setting of the instrument to the new location
on the other hand: changing coordinates of a location is fine in case of solving an error
agreed
How about asking the user if this is a relocation or correction when he changes the coordinates? Additionally we could put a notice next to the coordinate fields describing what happens when he changes them.
Possible sources:
I will start this now, using geonames.org and resque as job queue
As it is working now, should we close it? Or is there anything else?
Should be good for now - closing :)
When a Location gets created, we want to pull corresponding geo data and store it with the location.
We should do that in the background (e.g. with Delayed::Job) for the user not having to wait for the geo data.
Related: Latitude and longitude should be unalterable. When an instrument is being moved, a new location should be created, otherwise all related samples get moved, too.