Closed lecoqlibre closed 3 months ago
I don't think the ontology covers this currently, but let's check with @Alcoz
I'd prefer to use a gender-neutral term (seller
, or salesperson
). The relationship could be SoldBy
(not sure what the inverse relationship would be :thinking: ).
I'm also wondering about B-2-B sales - could the seller
be an Organisation ? Perhaps it should point to Actor, rather than Person ?
Also worth noting it would be empty in most cases (e.g. web-sales)... do we have a specific use-case/platform requesting this?
I'd prefer to use a gender-neutral term (seller, or salesperson).
+1 for "salesperson".
The relationship could be SoldBy (not sure what the inverse relationship would be 🤔 ).
OK for "soldBy". The inverse could be "sells"?
I'm also wondering about B-2-B sales - could the seller be an Organisation ? Perhaps it should point to Actor, rather than Person ?
We should think about it. There is the Coodination
object between an Enterprise
and a SaleSession
. But it's not really the same as different salespersons could have sold different orders during the same sale session. I guess it's OK for an enterprise to sell products of other enterprises? So the link could be between Order
and Agent
.
Also worth noting it would be empty in most cases (e.g. web-sales)... do we have a specific use-case/platform requesting this?
Yes I need it for the sale application I'm developing. I would like to track who has sold what.
Agreed it will be a relationship between Order
& Agent
: sells
and soldBy
Sometimes, we want to know who sold certain products.
For example, on a farm, several people can sell the farm's products. It's the same thing for a producers' store.
I don't think we handle this at the moment.
Proposal: add a salesman attribute to the Order concept. The attribute would point to a Person.