[Data-modeling] Proposed changes to the /organization/organization type

[Bryan Cheung]

> 2. One of the designers of the organization type originally created
> the property key_people, and later decided this was a bad idea and hid
> the property.  This property has been hidden for quite some time, but
> there still exists some data that should be migrated.
>
> The existing data should be migrated to /business/employer/employee
> (employer is an included type) and the hidden property should be
> deleted.


I'd like to to solicit feedback from the data-modeling gurus out there  
about this migration.  Organizations can have paid employees,  
volunteers or a combination of both.  While I believe the reasoning  
for getting rid of the ambiguous property "key person" is still valid,  
do people think the property  "employees and other personnel" on the  
employer type is sufficient in capturing a "key person" who is a  
volunteer?  An alternative  would be to have a volunteer property (on  
employer or organization type); however, this might be complicating  
because the reciprocating property would either have to be on the type  
person or a new type like "volunteer".

Suggestions?

Thanks,
Bryan


On Mar 5, 2008, at 11:36 AM, Bryan Cheung wrote:

> A couple of changes have been proposed for the /organization/
> organization type:
>
> 1. A user has requested that we add time span as a disambiguated
> property on organization member.
>
> http://www.freebase.com/view/discuss/organization/organization_member#%2Fguid%2F9202a8c04000641f8000000006fe1430
>
> I think it's a good idea to know when people were members of an
> organization; however, the relationship between an organization member
> and an organization is a simple one, and we would have to insert a CVT
> to represent the timespan-member relationship.
>
> 2. One of the designers of the organization type originally created
> the property key_people, and later decided this was a bad idea and hid
> the property.  This property has been hidden for quite some time, but
> there still exists some data that should be migrated.
>
> The existing data should be migrated to /business/employer/employee
> (employer is an included type) and the hidden property should be
> deleted.
>
> Does anyone disagree with this changes?  Are the applications being
> developed that will break due to these changes?
>
> Thanks,
> Bryan
>
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling