frederik at remote.org
Sun Feb 26 12:09:30 GMT 2012
On 02/26/2012 12:48 PM, waldo000000 at gmail.com wrote:
> ...if a decliner has added an object to a relation, then it will be
> removed from the relation, else it can remain
> What about a relation where /some /members were added by decliners? Just
> remove those members,
> or delete the entire relation,
> or flag it somehow
> as needing re-verification?
This is something we haven't yet talked about. We'll probably have some
kind of bot that creates new, clean versions of anything that has a
"problematic history"; such a bot could theoretically also add a tag like
note:relicensing=this object was modified in the relicensing process (X)
and needs to be checked, please remove this note after doing so
or whatever. "X" could be replaced by a list of actions taken on the
object: "tags removed", "tags changed", "nodes removed", "members
removed" or so.
But this might also be considered too much rubbish (a la
"tiger:revieved=no") in the database, and we could also simply, by
looking at the changesets that the bot creates, identify all objects and
versions touched by the bot and then regularly check whether any of them
have been changed by a mapper since (like the "TIGER edited map").
More information about the Rebuild