[Developers] Moving types to a different domain

[Ed Laurent]

My primary reason for making this request is because any new type not
purposefully created outside the default domain is placed there. So, if I
make a new type while describing the properties of an existing type, it goes
into the default domain instead of the domain of its parent type. I would
prefer that the default is that of the parent type and/or the user is given
an option to choose from like Gordon suggested. I don't need a batch
operation either.

Short answer:
1. Just a couple
2. Yes

-Ed


On Dec 17, 2007 8:10 PM, Stephanie Hornung <stephanie at metaweb.com> wrote:

> There's been some requests recently for a feature to move types to
> different domains within your own namespace, so its been pushed up a
> bit in the priority list (at least on the design side.)  I'm working
> on the interaction for this, so I have a few questions for those of
> you who have requested the feature:
>
> 1.  Do you find yourself needing to move a bunch of types at once, or
> is it usually just a couple (1-2)?
> 2.  If you are moving a a bunch of them, are they usually in one place
> and you want to move them to another?
>
> The most common use case I can see is that you'd create a few types in
> your default domain, and then realize that a bunch of them should be
> grouped together in a different domain.  Is this the case?  Or do you
> find that you've started with a domain or two and then realize that
> they should be organized differently, so you need to switch 'em all
> around?
>
> Thanks for your input!  Just want to make sure I understand the need
> before designing the feature for it.
>
> -Stephanie
>
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/developers/attachments/20071217/38458073/attachment.htm