WSS 3.0 在并行开发环境中管理同一文档的多个版本
我们在工作中使用 WSS 3.0 来管理我们系统的设计文档。我们在并行环境中工作，这意味着我们通常拥有文档的生产副本（例如文档 A）以及该文档的两个或多个版本，这些版本将由独立项目团队处理（文档 A（项目 1）和文档） A (proj 2))，我们过去通过将文档保存在单独的网站集中来实现这一点，但是这非常混乱，并且随着时间的推移，跟踪最新版本变得非常困难。
我想要实现的目标是将文档 A 的所有版本存储在同一个文档库中，保持名称相同，但使用元数据字段区分文档的不同版本，以便用户能够查看该文档的生产版本文档，而 proj 1 和 proj 2 可以单独处理其文档。文档的每个单独版本还必须可以使用 WSS 搜索进行搜索。
例如名称项目名称 文档A制作 文档 A 项目 1 Doc A Proj 2
我曾考虑过在库中简单地使用版本控制来维护文档的不同版本，并允许用户简单地转到版本历史记录来选择他们想要查看或处理的文档。这种方法的问题是我无法让文档的单独版本显示在搜索结果中。
我还坚持使用 WSS 3.0 至少 12 个月，因此我的解决方案必须基于 WSS 3.0。
有没有人有尝试实施类似的事情的经验，如果有的话，您使用的解决方案是什么？我无法想象我是唯一一个尝试迎合并行开发环境的人。
We are using WSS 3.0 at work to manage design documents for our systems. We work in a parallel environment which means we usually have a production copy of a document (e.g Doc A) plus also two or more versions of that document that will be worked on by independent project teams (Doc A (proj 1) & Doc A (proj 2)), we have in the past achieved this by keeping the documents in seperate site collections, however this is very messy and over time has become extremely hard to keep track of the latest versions.
What I am trying to achieve is to store all versions of Doc A in the same document library keeping the name the same but distinguish the different versions of the document using meta-data fields so that users will be able to view the production version of the document while proj 1 and proj 2 can work on their documents seperately. Each individual version of the document must also be searchable using the WSS search.
E.g Name Project Name
Doc A Production
Doc A Proj 1
Doc A Proj 2
I have thought about simply using version control in the library to maintain the different versions of the document and allow the users to simply go to version history to choose which document they want to view or work on. The issue with this approach is that I can not get the seperate version of the document to show up in the search results.
I am stuck with WSS 3.0 for at least another 12 months, so my solution has to be WSS 3.0 based.
Has anyone had experience trying to implement something similar and if so what was the solution that you used? I can't imagine that I am the only one trying to cater for a paraelle development environment.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
简短回答：重命名文档是解决方案（后修复某些内容以形成不同的文档名称）。
长答案：我有机会将庞大的文档库从 oracle 门户迁移到 MOSS 2007，并且我花了时间找出解决方案。最后，我最终在事件处理程序中手动/编程地进行了后修复版本。
问候，
阿泽尔
Short Answer: Renaming Document is the solution (Post-fixing something to make distinct document name).
Long Answer: I got chance to migrate huge document base from oracle portal to MOSS 2007 and I spent time to find out the solution. Finally I ended up post-fixing versions manually/programmatically in the event handler.
Regards,
Azher