the default behavior right now when we import a morph frequencies file is to add the imported frequencies to whatever the user already has in their local store for a given form. This could have the undesired impact of exponentially increasing frequency counts when the intent was simply to replace the local storage with the new data. The user should probably have to specify this explicitly - whether they are replacing existing data or augmenting it. The correct default behaviour may be to add frequency info where the form didn't exist already, but replace what exists, rather than adding.
the default behavior right now when we import a morph frequencies file is to add the imported frequencies to whatever the user already has in their local store for a given form. This could have the undesired impact of exponentially increasing frequency counts when the intent was simply to replace the local storage with the new data. The user should probably have to specify this explicitly - whether they are replacing existing data or augmenting it. The correct default behaviour may be to add frequency info where the form didn't exist already, but replace what exists, rather than adding.