产品类别与业务类别

发布于 2024-12-19 20:30:02 字数 674 浏览 3 评论 0原文

我正在开发一个电子商务网站,但遇到了一个问题。我需要满足的要求是:给定用户输入的特定字符串,如“lock”、“tennis”、“cinema”或“scaffold”,我应该显示与该查询匹配的个人资料和产品发布。

这使我得出以下结论:

a) 我应该对个人资料(他们做什么)进行分类:也许是某种“业务类别”。我在这里面临一个问题,创建一个涵盖世界上所有业务活动的列表几乎是不可能的,所以我在这里阅读了一些很好的问题,并且喜欢创建 1 或 2 级层次结构然后捕获用户的策略通过可重复使用的标签自动反馈。

这里的想法是保留更有可能被想到的关键字,因此最有可能被搜索。

顺便问一下,是否有我缺少的非常好的业务类别列表?

b) 我应该对产品和服务(它们提供的内容)进行分类:通过类似的方法,我喜欢使用一些固定类别,然后让用户使用持久标签。我再次问你是否有一个类别列表真的很震撼。

问题:

1)你喜欢我刚才描述的内容吗?根据您的经验,您认为这可能有效还是我会被淹没在标签海中?

2)有时产品和业务层次结构都是多余的。有些人将他们的业务描述为“剧院”、“银行”、“牙医”,但这不是产品或服务,而是它们的实际情况。但很多情况下人们会说“(销售/制造)汽车”、“(制造)陶器”等等。他们的商业活动主要取决于他们销售或生产的产品或服务。您对此有何看法?

I'm developing an e-commerce site and I'm facing a problem. The requirement I need to fulfill is: given a certain string like "lock", "tennis", "cinema" or "scaffold" entered by an user, I should display both profiles and product postings matching that query.

That leads me to these conclusions:

a) I should classify profiles (what they do): maybe some sort of "business category". I face a problem here, it's almost impossible to create a list that covers all the business activities in the world, so I've been reading some good questions here and liked the strategy of creating a 1 or 2 level hierarchy and then capture the user feedback automatically through reusable tags.

The idea here is to keep the keywords that are more likely to be thought of and so with best odds of being searched for.

By the way, is there a really good business category list out there that I'm missing?

b) I should classify products and services (what they offer): with a similar approach, I liked using some fixed categories and then let users use persistent tags. I ask you again if there is a category list out there that really rocks.

Questions:

1) Do you like what I've just described? Based on your experiences do you think it might work or will I drown in a tag sea?

2) Sometimes both product and business hierarchies are kind of redundant. There are some people that describe their businesses like "theater", "bank", "dentist" and that's not a product or service but rather what they actually are. But there are plenty of cases where people say "(sale/manufacturing) cars", "(manufacturing) pottery", and so on. Their business activity is chiefly determined by the product or service they're selling or producing. What's your take on this?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

似最初 2024-12-26 20:30:02

我做了类似这样的事情:ror_ecommerce。我使用了产品类型树。

所以你可以卖:

家具 =>客厅=> 按客厅过滤的椅子

也会给出具有指向椅子的product_type 的项目。

为了让它变得更复杂,我会首先与业务人员战斗。
其次,我将创建一个模型,其中产品具有许多产品类型。因此,您需要一个product_type 和product 之间的联接表。

回答你的问题:

1)你可能会被淹没,因为类别是无限的。限制标签数量或创建一个可供业务人员填充的管理界面。如果不是,您的业务人员会要求您一遍又一遍地做这项工作。

2)听起来你的树看起来像这样:

  • 销售/制造=>汽车
  • 销售/制造 =>陶器
  • 银行=>个人
  • 银行=> 因此,

如果有人只想要一家银行,他们会得到个人和企业的结果。但他们可以进一步将搜索细化为个人银行业务。

听起来业务和产品层次结构也是完全多余的。我真的会反对一个业务人员说任何其他话,因为未来的要求将是将业务和个人层次结构联系起来。如果它们相同,那就很容易了。您可能需要在个人/企业/两者列表上添加类型标志。如果不需要,删除该标志会容易得多。

祝你好运

I did something like this is ror_ecommerce. I used a tree for product_types.

So you could sell:

Furniture => Livingroom => Chairs

Filtering by Livingroom would also give items that have a product_type pointing to Chairs.

To make it more complex I would first fight the business person.
Second I would create a model where product has many product_types. Thus you need a join table between product_type and product.

Answer to your question:

1) You will probably drown because categories are infinite. Limit the number of tags or make an admin interface that your business people can populate. If not your business folks will request you to do this work over and over again.

2) It sounds like Your tree would look like this:

  • sale/manufacturing => cars
  • sale/manufacturing => pottery
  • bank => personal
  • bank => business

thus if someone just wants a bank they get results for personal and business. but they can further refine the search to just personal banking.

It also sounds like the business and product hierarchies are completely redundant. I would really fight a business guy saying anything else because a future requirement will be to relate business and personal hierarchies. If they are the same it will be easy. You might want a type flag on the list for personal / business / both. it will be a lot easier to remove the flag if it's not needed.

Good Luck

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文