Introducing Document Management in SharePoint 2010 介绍SharePoint 2010中的文档管理

本文主要是介绍Introducing Document Management in SharePoint 2010 介绍SharePoint 2010中的文档管理,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

Introducing Document Management in SharePoint 2010  

介绍SharePoint 2010中的文档管理

        This time I want to talk to you today about another key area of the content management world: Document Management (DM). Over the next few months, you’ll be hearing from several members of the engineering team about new DM features that help you get the most value out of your document corpus. We’ll also discuss how key early adopters of SharePoint 2010 used new DM features to solve the toughest information governance challenges.
        Today, though, I’d like to spend time talking about what the team has learned about the document management space since SharePoint 2007 and take you on a journey through the key tenets that guided our DM vision this release.

Recap: Document Management in SharePoint 2007 回顾:SharePoint 2007 中的文档管理

        SharePoint 2007 was the first release where SharePoint really broke out of its collaboration role and enabled customers to apply structure and management to their document libraries. A lot of the key DM infrastructure was established in that release: Check in/Check Out, Major/Minor Versioning, Per-Item Permissions, Content Types, Workflows, and the Recycle Bin are just a few examples. Of course, all of these features tightly integrated with the Office client applications such as Word, Excel, and PowerPoint to make it simple for end users to interact with the document repository (a core design tenet that carries through in 2010).
        Features like these enabled customers to start creating high-value knowledge repositories on SharePoint 2007.
        For 2010, we looked to build off of 2007’s gigantic success, and we rallied our designs around three key ideas:

Tenet #1: Manage the unmanaged

        As we looked at how our customers were starting to use the 2007 system’s DM features, we noticed an interesting trend: These features were not just part of managed document repository deployments. Indeed, the traditional DM features were getting heavy usage in average collaborative team sites as well. Customers were using them to apply policy and structure as well as gather insights from what otherwise would have been fairly unmanaged places. SharePoint was being using to pull more and more typically unstructured silos into the ECM world.
        This is a key insight that really drove our investments in SharePoint 2010. For instance, one of our key new features in SharePoint 2010 is the notion of a Document Set. You can think of a document set as a “folder on steroids.” It allows you to group related documents together so that they share metadata and have a common homepage, workflows, and archival process:
        The Welcome Page of a document set is a customizable page that allows users to discover the content in the set, view and sync metadata between items in the set, and manage the set.
        When it came time to design this feature, we knew people would want to use it to manage very structured and rigid official processes (e.g. a pharmaceutical company submitting forms to a regulatory agency). But equally important to us was that the feature can be used in a lightweight team site to manage most processes that requires multiple documents to be bound together (e.g. a team that just needs to put together a pitch book/sales proposal that includes a PowerPoint deck, a spreadsheet of costs, and a document that describes the sales pitch).
        Enabling the document set feature to be used informally and easily is one way we are expanding the value of ECM in the minds of SharePoint end users.

Tenet #2: Social computing and enterprise metadata are game changers.

        As we started to design out the DM feature set for this release, we quickly realized the power of metadata – both structured taxonomies as well as lightweight folksonomies (keywords) – as transformative forces in the document management space. A SharePoint 2010 document repository would need to take full advantage of both concepts.
        There are two key principles that enable SharePoint 2010 users to take advantage of metadata. First is on the tagging side: it’s easy for a site to use enterprise wide content types and taxonomies and it’s also simple for a user to tag with them.
        SharePoint 2010 offers consistent management of metadata that any SharePoint site can hook in to with virtually no effort. This allows the entire enterprise to be talking the same language. Tangibly, you can do things such as define the list of products you sell once and have that data available in any SharePoint site.
        Note how the type-ahead functionality makes it easy for a user to pick a value from this folksonomy. Also note how the West Coast tag was automatically filled out for the user because it was set as the default value for all documents in this library.
        The second key principle is how SharePoint takes advantage of these tags. For instance, a SharePoint 2010 document library can be configured to use metadata as a primary navigation pivot. You can think of metadata based navigation as a virtual folder structure that can be used to filter the items in the library:
        Instead of navigating by traditional folders, a user filtered the library to the virtual folder that contains just sales materials about Contoso’s tent products.
        It’s a virtuous cycle here: Easy metadata entry allows items to be tagged, which can drive navigation. And because users need the metadata to navigate the repository, this incentivizes them to tag the items!

Tenant #3: The browser as a powerful document management application.

        SharePoint has always been used for many scenarios, but perhaps it’s known best for two things:
· A best of breed tool for creating web pages and sites
· A place to store, manage, and collaborate on documents
        SharePoint 2010 makes a big bet that creating a knowledge management repository requires the merger of both of these worlds. The browser is increasingly becoming the key technology for information workers – both inside the corporate firewall and on the consumer front. Sure, people will always want to download documents to take with them – but they also want to use the browser to interact with the document and see a wealth of context about the document (e.g. metadata, related documents, wiki pages about the document’s topic).
        It’s time for the industry to expect any document management system to also be great at creating pages or wikis that add context to the documents’ content. And any system that doesn’t is going to start looking antiquated.
        SharePoint 2010 delivers on this vision in a few different ways. First, if you’ve installed the Office Web Apps (licensed as part of the Office 2010 suite), the default click for a document library can be configured to load Office documents in the browser:
        Without ever leaving the browser, users can quickly view Office documents stored in SharePoint.
        Second, we spent a lot of time this release thinking about how the web content management features can be used in document repositories. For instance, the ever popular Content Query web part can be used to roll up all the documents related to a particular topic:
        A content steward might create a page about a particular topic (e.g. a new product). This page includes text about the product, marketing pictures, as well as roll ups of all the documents tagged with the product.
        This vision allows you to combine two very powerful aspects of SharePoint into one solution to your organization’s knowledge discovery problem. It’s a merger of an enterprise wiki and a traditional enterprise document repository.

Wrapping up: A lot more to come!

        I hope this post gives some context on where we are going with document management in SharePoint 2010 and beyond. Feature wise, we really only hit a few of the many DM features that make up SharePoint 2010 – stay tuned for future posts as we deep dive into a lot more! And feel free to leave comments about what you’d like us to blog about (especially if you’ve downloaded the Beta and given SharePoint 2010 a test drive already!)

这篇关于Introducing Document Management in SharePoint 2010 介绍SharePoint 2010中的文档管理的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/1083096

相关文章

性能测试介绍

性能测试是一种测试方法,旨在评估系统、应用程序或组件在现实场景中的性能表现和可靠性。它通常用于衡量系统在不同负载条件下的响应时间、吞吐量、资源利用率、稳定性和可扩展性等关键指标。 为什么要进行性能测试 通过性能测试,可以确定系统是否能够满足预期的性能要求,找出性能瓶颈和潜在的问题,并进行优化和调整。 发现性能瓶颈:性能测试可以帮助发现系统的性能瓶颈,即系统在高负载或高并发情况下可能出现的问题

水位雨量在线监测系统概述及应用介绍

在当今社会,随着科技的飞速发展,各种智能监测系统已成为保障公共安全、促进资源管理和环境保护的重要工具。其中,水位雨量在线监测系统作为自然灾害预警、水资源管理及水利工程运行的关键技术,其重要性不言而喻。 一、水位雨量在线监测系统的基本原理 水位雨量在线监测系统主要由数据采集单元、数据传输网络、数据处理中心及用户终端四大部分构成,形成了一个完整的闭环系统。 数据采集单元:这是系统的“眼睛”,

Hadoop数据压缩使用介绍

一、压缩原则 (1)运算密集型的Job,少用压缩 (2)IO密集型的Job,多用压缩 二、压缩算法比较 三、压缩位置选择 四、压缩参数配置 1)为了支持多种压缩/解压缩算法,Hadoop引入了编码/解码器 2)要在Hadoop中启用压缩,可以配置如下参数

综合安防管理平台LntonAIServer视频监控汇聚抖动检测算法优势

LntonAIServer视频质量诊断功能中的抖动检测是一个专门针对视频稳定性进行分析的功能。抖动通常是指视频帧之间的不必要运动,这种运动可能是由于摄像机的移动、传输中的错误或编解码问题导致的。抖动检测对于确保视频内容的平滑性和观看体验至关重要。 优势 1. 提高图像质量 - 清晰度提升:减少抖动,提高图像的清晰度和细节表现力,使得监控画面更加真实可信。 - 细节增强:在低光条件下,抖

活用c4d官方开发文档查询代码

当你问AI助手比如豆包,如何用python禁止掉xpresso标签时候,它会提示到 这时候要用到两个东西。https://developers.maxon.net/论坛搜索和开发文档 比如这里我就在官方找到正确的id描述 然后我就把参数标签换过来

图神经网络模型介绍(1)

我们将图神经网络分为基于谱域的模型和基于空域的模型,并按照发展顺序详解每个类别中的重要模型。 1.1基于谱域的图神经网络         谱域上的图卷积在图学习迈向深度学习的发展历程中起到了关键的作用。本节主要介绍三个具有代表性的谱域图神经网络:谱图卷积网络、切比雪夫网络和图卷积网络。 (1)谱图卷积网络 卷积定理:函数卷积的傅里叶变换是函数傅里叶变换的乘积,即F{f*g}

软考系统规划与管理师考试证书含金量高吗?

2024年软考系统规划与管理师考试报名时间节点: 报名时间:2024年上半年软考将于3月中旬陆续开始报名 考试时间:上半年5月25日到28日,下半年11月9日到12日 分数线:所有科目成绩均须达到45分以上(包括45分)方可通过考试 成绩查询:可在“中国计算机技术职业资格网”上查询软考成绩 出成绩时间:预计在11月左右 证书领取时间:一般在考试成绩公布后3~4个月,各地领取时间有所不同

安全管理体系化的智慧油站开源了。

AI视频监控平台简介 AI视频监控平台是一款功能强大且简单易用的实时算法视频监控系统。它的愿景是最底层打通各大芯片厂商相互间的壁垒,省去繁琐重复的适配流程,实现芯片、算法、应用的全流程组合,从而大大减少企业级应用约95%的开发成本。用户只需在界面上进行简单的操作,就可以实现全视频的接入及布控。摄像头管理模块用于多种终端设备、智能设备的接入及管理。平台支持包括摄像头等终端感知设备接入,为整个平台提

计算机毕业设计 大学志愿填报系统 Java+SpringBoot+Vue 前后端分离 文档报告 代码讲解 安装调试

🍊作者:计算机编程-吉哥 🍊简介:专业从事JavaWeb程序开发,微信小程序开发,定制化项目、 源码、代码讲解、文档撰写、ppt制作。做自己喜欢的事,生活就是快乐的。 🍊心愿:点赞 👍 收藏 ⭐评论 📝 🍅 文末获取源码联系 👇🏻 精彩专栏推荐订阅 👇🏻 不然下次找不到哟~Java毕业设计项目~热门选题推荐《1000套》 目录 1.技术选型 2.开发工具 3.功能

C++——stack、queue的实现及deque的介绍

目录 1.stack与queue的实现 1.1stack的实现  1.2 queue的实现 2.重温vector、list、stack、queue的介绍 2.1 STL标准库中stack和queue的底层结构  3.deque的简单介绍 3.1为什么选择deque作为stack和queue的底层默认容器  3.2 STL中对stack与queue的模拟实现 ①stack模拟实现