If they’re going to be functionally identical, why not just use one entity type for it and be able to designate whether a specific instance of that entity is an individual or a collective?
In MusicBrainz I sometimes leave the “type” blank exactly because I don’t know if something is “Group” or “Person”, I could imagine the same being true here, and the proposed change would force editors to make a call on this property before being able to create the entity at all, which means that sometimes the call will be wrong and it will have to be changed later—and I think it will probably be harder to change an entity’s entity type than an attribute of it.
6 Likes