版本控制不足,MOSS 2007

发布于 2024-08-15 22:49:05 字数 323 浏览 12 评论 0原文

用于行政和临床(医疗保健)政策和程序的 Sharepoint 文档库。

版本控制和审批工作流程支持立法要求并防止责任问题。

不幸的是,删除文档会删除它曾经存在的所有记录 - 所有历史记录都会随之消失。

我现在没有沙箱来验证,但我认为它也绕过了审批工作流程。

从法律上讲,对于其中一些,如果我们删除它,我们仍然必须能够显示该政策在特定地点/时间的内容。

是否有相当简单的修复或解决方法?

同样,如果有人更改了文件名(意外更改文件名并不难),两个文件名都需要显示历史记录。

Sharepoint document libraries used for policies and procedures, both administrative and clinical (health care).

version control and approval workflows support legislative requirements and protect against liability issues.

Unfortunately, deleting a document removes all record that it ever existed--all the history goes with it.

I don't have a sandbox right now to verify, but I think it also bypasses the approval workflow.

Legally, for some of these, if we delete it, we still MUST be able to show what the policy was at a particular place/time.

Is there a reasonably simple fix or workaround?

Similarly, if someone changes the filename (which is not hard to do accidentally), both file names need to show the history.

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

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

发布评论

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

评论(5

葬シ愛 2024-08-22 22:49:05

我向管理层推荐的解决方案是使图书馆无法进行删除。可以通过创建一个表明不再使用的新主要版本来“删除”策略/过程。

更新:我们确实采取了这种方法,而且它确实有效。 “删除”文档是通过制作空版本来完成的。历史仍然是为了让法律人士满意。

The solution I am recommending to management is to make deletion unavailable from the library. A policy/procedure can be "deleted" by creating a new major version that say it is no longer to be used.

UPDATE: We did take that approach, and it does work. "Deleting" a document is done by making an empty version. The history remains to satisfy the legal folks.

习惯成性 2024-08-22 22:49:05

没有一个容易想象的地方可以看到所有已删除的记录(即,这将是图书馆本身的某些特定视图,但 MOSS 没有为我们提供一个)。一个简单的解决方法是将“已删除”列添加到隐藏在用户表单中的列表中。然后,您将在事件处理程序中捕获“ItemDeleting”事件并将“deleted”设置为true(但实际上不删除该项目)。当然,您必须过滤用户看到的所有视图,以便仅显示已删除= false 的项目。

There is no easy place to imagine where you could see all the deleted records (i.e. that would be some specific view of the library itself but MOSS doesn't provide us with one). A simple workaround would be to add a "Deleted" column to the list which is hidden in user forms. Then you would then catch the "ItemDeleting" event in an eventhandler and set the "deleted" to true (but in fact not delete the item). Of course, you have to filter all the views that the user sees so that only deleted=false items are shown.

束缚m 2024-08-22 22:49:05

这就是它的工作原理。我认为这不充分,因为 SharePoint 不是一个版本控制系统,而是一个文档管理系统。从这个角度来看,从存储库中删除某些内容意味着“我不想再看到它”。

来自此处

您可以选择删除文件的单个版本 - 例如,如果您知道在该版本中犯了错误 - 这会从版本历史记录中删除该版本。但是,如果删除实际文件,则其所有版本都会随之删除。默认情况下,当您删除版本时,该版本会被发送到回收站,您可以在回收站中恢复该版本,直至永久删除。但是,您的组织可能会以不同的方式处理删除。

我的车不会漂浮,但它的设计从来就不是为了漂浮。如果我想要漂浮的东西,我会买一艘船。因此,它与技术相关 - 如果您需要诸如永久保留已删除对象之类的功能,那么 SharePoint 可能不适合您或您的组织。

That's the way it works. I don't think it's inadequate insofar as SharePoint is not a version control system, but rather a document management one. From that standpoint, deleting something from the repository means "I don't want to see it again".

From here:

You can choose to delete a single version of a file — for example, if you know that you made a mistake in that version — which removes that version from the version history. However, if you delete the actual file, all of its versions are deleted with it. By default, when you delete a version, the version is sent to the Recycle Bin, where it can be recovered until it is permanently deleted. Your organization may handle deletions differently, however.

My car doesn't float, but then it was never designed to do that. If I wanted something that floats, I would buy a boat. So it goes with technology - if you needed a feature like keeping a deleted object forever then SharePoint is probably not the right product for you or your organization.

花伊自在美 2024-08-22 22:49:05

一种解决方案是:

  1. 创建列表文档审核历史记录
  2. 使用 EventReceiver 上的 ItemAdded、ItemUpdated、ItemDeleting 和其他(如果您愿意)(ItemFileMoved 等),然后将适当的记录添加到此列表。

第二个是:

  1. 在 ItemDeleting 事件中,您还可以
    取消删除的执行
    操作并移动文档
    其他地方,如果你愿意的话。

One solution would be:

  1. Create list Document Audit History
  2. Use EventReceiver on ItemAdded, ItemUpdated, ItemDeleting and others if you wish (ItemFileMoved etc) and then add appropriate records to this list.

Second one would be:

  1. On ItemDeleting event you can also
    cancel the execution of delete
    action and just move document
    somwhere else, if you wish so.
静水深流 2024-08-22 22:49:05

我听说 M$ 有一个补丁,但我不记得在哪里听到的,而且我还没有在网上找到它。

I heard that M$ had a patch for it but I can't remember where I heard that, and I haven't found it online yet.

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