[Developers] type checking?

[Dan Milbrath]

ah, perhaps I misunderstood your suggestion. Defining incompatible  
types might be a little tricky, but we could look at alerting someone  
if a type is being added that isn't commonly found paired with  
another type.

The first couple items you list are already being worked on. We will  
take a look at your other ideas too.

Thanks,
Dan



On Dec 3, 2007, at 3:56 PM, Arthur van Hoff wrote:

> There should be no confirmation necessary when the type of the  
> selected object matches the type of the property. It is only when  
> you add a new type to an object that a confirmation step can help  
> to avoid mistakes. Here are some improvements that can be made in  
> the UI:
>
> -       Improve the relevance matching:
> o    List objects of the appropriate types first.
> o    List objects that have “compatible” types second. (i.e. /music/ 
> actor is compatible with /film/actor since they both include / 
> people/person).
> -       Add a confirmation step when a new “incompatible” type is  
> added to an object.
> -       Provide an easier mechanism to undo changes (i.e. undo  
> everything I did today, undo that last thing I just did, etc..)
>
> I’m not suggesting that we make it harder to enter data, just that  
> we make it harder to make mistakes when entering data.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/developers/attachments/20071203/449ea1b7/attachment.htm