子网站的网站栏默认值
我正在尝试弄清楚如何实现以下场景。我有多个具有相同结构的项目网站（该结构包含子网站和库）。我想用项目编号标记每个文档（例如 100-050-BCD）。我如何将其设置为网站集中每个子网站的默认值，以便用户不必一遍又一遍地填写数字。
我的第一种方法是在网站集级别创建内容类型“合同”，其中包含网站列（标题、描述、项目编号等），但我无法为每个子网站设置值。正确的？所以我认为这是行不通的。
对于第二种方法，我将使用托管元数据。我将在子网站级别创建一个名为“projectnumber”的列，并使用托管元数据存储中的默认值。因此，在元数据存储中，我创建项目编号并将其设置为子站点列类型中的默认值。此栏已添加到子网站的库中。然后我应该能够使用元数据作为我的搜索结果的细化，或者不？其中丑陋的部分是我为每个子网站都有不同的列类型“projectnumber”，感觉不太正确。
问题是我使用的是正确的方法还是应该使用另一种方法，这可以更容易完成吗？
I am trying to figure out how to implement the following scenario. I have multiple project sites with the same structure (the structure contains subsites and libraries). I want to tag each document with a projectnumber (eg 100-050-BCD). How can i set this as default for each subsite in the site collection, so the user does not have to fill in the number over and over again.
My first approach was to create a content-type "contract" on site collection level which contains the site columns (Title, Description, Projectnumber etc) but i cannot set a value for each subsite. Right? So i think this could not work.
with the second approach i would use managed metadata. I would create a column on the subsite level called projectnumber with a default value from the managed metadata store. So in the metadata store I create the projectnumbers and set this as default in the subsite column type. This column is added in the libraries in the subsite. I then should be able to use the metadata as refinement in my searchresults, or not? The ugly part in it is that i have different column types "projectnumber" for each subsite, that feels not quite right.
The question is am i using the right approach or should i use another one and could this be done much easier?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
你用标签做什么？是为了搜索吗？
我可能会让网站集 url 包含项目代码。例如
http://yoursite/projects/100-050-BCD
这样，如果有人搜索对于 100-050-BCD，应返回项目网站集中的所有内容。他们可以根据需要添加额外的过滤器。
该 url 还可以用于标准搜索细化（在搜索结果页面的左侧），因此如果有人搜索“工作请求”，那么他们可以按 url 进行过滤（这将按项目进行过滤）
What are you using the tag for? Is it for searching?
I would probably make the site collection url contain the project code. eg
http://yoursite/projects/100-050-BCD
So that way, if someone searchs for 100-050-BCD, everything in the project site collection should be returned. They can add extra filters as they need to.
The url can also be used in the standard search refinements (on the left of the search results page), so if someone searchs for eg "work request", then they can filter by url (which would be filtering by project)