5 things you should know about SharePoint 2007 Records Center

本文探讨了SharePoint 2007中记录中心站点模板的一些独特特性,这些特性区别于常规的团队或协作站点模板。重点介绍了文档库无法保存为模板、权限继承断裂、无法删除文档库等问题,并详细解释了记录路由列表的功能及其管理方式。

文章转载自arbindoc

For past couple of months, I have been working on large implementation of Records Center site in SharePoint 2007. During this time, I have come across few features in Records Center site template that are quite different from a regular SharePoint site template such as Collaboration and Team site template. Obviously, the Records Center comes with Hold infrastructure that consists of Holds List and Record Routing List, but these features make document library function differently. I spent considerable amount of time trying to research why document libraries are not functioning the way I would expect them in a Team or a Collaboration Site. There is nothing wrong in functionality, it is just that there is not much information around how document libraries in Records Center function differently in Records Center

I hope by sharing my information, people implementing Records Center can save time researching on this topic.

1. Cannot save library as Template:

When you create a new document library, you will notice that it functions the same way as you would expect a document library to function. Things get little different as soon as you have a single document put on hold. The first thing you will notice that “Save document library as template” link disappears from Settings. Even before a document is placed on hold, if you click on that link and save the document library as template, you will not see the template in the Create screen. In short, you cannot save document libraries as template and use the template to create new document library.

Interestingly, you could create a List Template Feature and publish a library template. You are just not allowed to do it using User Interface.

2. Library Permission inheritance is broken:

A new document library, by default, inherits permission from Site Collection. When you go to Document Library –> Settings –> Document Library Settings –> Permissions for document library, you will see that permissions are inherited and not broken. However, as soon as you create a Record Routing entry with location pointing to your document library, the permission inheritance is broken. So adding new users / groups in site collection, will not make it the library.

3. Cannot Delete Document Library:

Similar to point 1, Delete this document library link disappears from document library settings screen as soon as a Routing Entry is created in Record Routing List that points to new document library. This means, you will not be able to delete the document library as long as the library has a document with hold, or there is a routing entry in Record Routing List that points to document library. As soon as the Record Routing entry is deleted, you will notice that Delete this document library link appears in the Document library settings. One other important point to note is that the user deleting the routing entry should be Site Collection administrator. If the routing entry is deleted by non Site collection administrator, then the delete link is not brought back.

4. Record Routing List:

Several activities happen behind the scene when a new Record Routing entry is created. Before we get to that, it is important to note that Record Routing List is supposed to be managed only by Site Collection Administrators. This list’s permission does not inherit from Site Collection. By default, this list has Viewers and Records Center Web Service Submitters with View Only and Read permission respectively. You could add  a SharePoint group or a user to the library with Full Control or Contribute permission, and that will allow that group / user to add, edit and delete entries. However, deleting a routing entry will not bring back Delete this document library link in the document library. See point 3 for more details.

When a new routing entry is created, the document library that is specified in the Location goes through few changes:

a. Permission inheritance is broken for the document library (See point 2)

b.. Save this document library as template link disappears from Document Library Settings. This link anyways is of no help (see point 1)

c. Delete this document library link disappears from Document Library Settings (See point 3).

5. Release Active Hold:

I, like many others, assumed that if a user has contribute permission on the Holds list, the user could Add, Edit a new hold or Release an existing hold. Though Add and Edit is possible using Contribute permission, Release hold requires Manage List permission level checked.

Based on all the above findings, I have concluded that Record Routing List should always be managed by Site Collection Administrator. Though, this is not obvious in the tool as you can add other users in the permissions, it causes unexpected behaviors in document libraries.

After thinking about the working of Records Center, I believe the way it is designed is aligned with how a Records department works in an organization. There are typically number of attorneys grouped by area of specialty responsible for a litigation. Also there are only few Records Manager responsible for all litigation holds. Litigations are sensitive in nature and therefore shared with only handful of people that are working on a particular litigation.

When a routing entry is created, permission inheritance is broken in the library. This ensures that any new user or a group added to site collection do not get access to the content that are held for litigation. Save library as template is disabled to prevent content on hold to be saved  as template. Delete this document library is disabled to prevent even Site Collection Administrators from deleting content or library that is being held until the hold is released. Though attorneys are responsible for individual holds that they manage, they are not allowed to add, delete or change record routing entries. Record Routing entries have global impact (in context of Records Center), as content from multiple content type can be routed to single library. Therefore, only handful of users – Site Collection Administrators – are responsible to Record Routing entries.

Hope some people saves time by reading this.

 

考虑柔性负荷的综合能源系统低碳经济优化调度【考虑碳交易机制】(Matlab代码实现)内容概要:本文围绕“考虑柔性负荷的综合能源系统低碳经济优化调度”展开,重点研究在碳交易机制下如何实现综合能源系统的低碳化与经济性协同优化。通过构建包含风电、光伏、储能、柔性负荷等多种能源形式的系统模型,结合碳交易成本与能源调度成本,提出优化调度策略,以降低碳排放并提升系统运行经济性。文中采用Matlab进行仿真代码实现,验证了所提模型在平衡能源供需、平抑可再生能源波动、引导柔性负荷参与调度等方面的有效性,为低碳能源系统的设计与运行提供了技术支撑。; 适合人群:具备一定电力系统、能源系统背景,熟悉Matlab编程,从事能源优化、低碳调度、综合能源系统等相关领域研究的研究生、科研人员及工程技术人员。; 使用场景及目标:①研究碳交易机制对综合能源系统调度决策的影响;②实现柔性负荷在削峰填谷、促进可再生能源消纳中的作用;③掌握基于Matlab的能源系统建模与优化求解方法;④为实际综合能源项目提供低碳经济调度方案参考。; 阅读建议:建议读者结合Matlab代码深入理解模型构建与求解过程,重点关注目标函数设计、约束条件设置及碳交易成本的量化方式,可进一步扩展至多能互补、需求响应等场景进行二次开发与仿真验证。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值