sharepoint 列出设计实践
我是 sharepoint 开发的新手，希望我的问题有意义，
使用 sharepoint 2010， 我正在开发的应用程序的结构如下所示：
- 网站集根
- 以下所有网站都通用的一些列表和内容类型。
- 一个从事 x 类型项目的网站
- 一个用于处理 y 类型项目的网站
- 一个用于执行与项目不直接相关但可能间接相关的其他内容的网站
如果我正在设计传统数据库应用程序，我将有一个 BaseProject实体，并且会通过 projectType 字段区分子项目，甚至会具有与 baseProject 实体 1-1 相关（某种继承关系）的子实体 - 如果规范化问题很困扰我。
周围的人建议为具有不同工作流程、文档模板、不同用户等的 x,y 项目建立单独的列表，并隔离不同站点的内容，在报告时聚合数据，甚至不考虑实体之间类似继承的关系但这意味着来自共同实体的关系需要分别与不同的项目列表建立。并且许多查找列表将围绕不同的“项目”实体列表重复。因此，未来扩展数据模型将是困难的。对于对整个应用程序范围感兴趣的报告，需要汇总分散在站点之间的列表。
如果我将列表设计为稍后可扩展
根站点中只有一个带有projectType列的baseProject列表： 我必须过滤包含超出特定站点中所需内容的每个列表
，根站点中的一个基本项目列表和其他类型的子列表 子站点中的项目：我需要同步基本列表和子列表之间的数据。拥有 baseProject 列表中的所有项目项。
问题是：设计共享点列表以建模实体之间的继承的最佳实践是什么？
问候..
I am new the sharepoint development, hope my question makes sense,
using sharepoint 2010,
structure of the application I am working on is like below:
- site collection root
- some lists and content types that are common to all sites below.
- a site for doing something with x-type projects
- a site for doing something with y-type projects
- a site for doing other stuff not directly related to the projects but may be indirectly
if I was designing a tratidional database application, I would have a BaseProject entity, and would discriminate the sub projects by a projectType field or even would have subEntities which are related 1-1 (kind of inheritace relationship) to the baseProject entity-if normalization issues bother me much.
people around suggest to have seperate lists for x,y projects which have different workflows, document templates, different users, etc, and isolate the contents of different sites, aggerate the datas when reporting, not even to think of inheritance-like relations between entities but this means the relations from common entities would need to be made seperately to the different lists of projects. and many look-up lists would be repeated around different lists of "project" entities. so expanding the data model would be difficult in the future. and for the reports that are interested in whole scope of the application, would need to aggregate the lists scattered among the sites.
if I design the lists to be more expandable later on
only one baseProject list in root site with a projectType column:
I would have to filter every lists that contains more than what I need in a specific siteone baseProject list in root site and sub-lists for other types of
projects in sub sites: I would need to syncronize the data between base list and sub lists. to have all the project items in baseProject list.
the question is: what are the best practices to design sharepoint lists to model inheritance between entities ?
regards..
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果没有更多关于该项目的细节，很难具体回答。构建场地模型是一项复杂的任务，特定于特定的项目要求。
简单来说，如果一个列表具有与之关联的不同处理，那么它就是一个单独的列表。如果您需要指示相似的数据，请使用定义的字段，这将保持一致性。无论您的结构如何，报告都可以发挥作用，因此请将此视为较小的问题。
但网站设计的主要关注点应该是业务的功能行为。如果你匹配得正确，那么其他一切最终都会水到渠成。
It is very difficult to answer specifically without a lot more detail on the project. Building your site model is a complex task that is specific to a particualar projects requirements.
In simple terms, if a list has different processing associated with it, then it is a separate list. If you need to indicate similar data, then use defined fields, which will maintain your consistency. Reporting can be made to work whatever your structure, so treat that as a lesser issue.
But the primary focus for site design should be the functional behaviour of the business. If you match that correctly, then everything else will eventually fall into place.