Posts Tagged ‘content type’

MetaVis Platform Features Overview: Copy content types with dependencies

March 29, 2011

A content type is a reusable collection of metadata (fields) and other settings that could be applied to SharePoint items. A content type in SharePoint may have a parent content type, which in turn may have another parent and so on. A content type may also have fields some of which it can inherit from its parents and the other fields could be created right inside this content type. Content types could also be added to lists or libraries that allows them to be used to assign metadata values to items or documents.

This way, content types form pretty complex structure in SharePoint site collections. Look at the example below generated by MetaVis Architect

 

 

 

MetaVis Migrator for SharePoint can copy all content types including their complete parent hierarchy and fields when a user copies a list or library that used these content types. MetaVis Migrator also reproduces source content type hierarchy in the target environment when copying the whole site.

 

Recently we added the function that allows users to copy just one selected content type from one site to the other one in one operation including all tree of the parent content types and all fields in these content types.

 

Select source and target sites in MetaVis Navigation Tree, Start Compare, expand Content Type compare area, select the content type to copy and click Copy from Left to Right button (or Copy from Right to Left button depending of the circumstances)

 

 

Using this operation MetaVis Migrator will copy the selected content type and all its dependencies.

 

MetaVis Change Manager allows scheduling content type copy activities using simple copy / paste or drag-n-drop gesture on MetaVis Navigation Tree. Unlike MetaVis Migrator, Change Manager displays content types in the navigation tree and allows copying them between different sites.

 

 

A part of MetaVis Change Manager functionality is to execute activities for multiple source and target site pairs provided by Excel spreadsheet. This function allows to mass-distribute content types between multiple site collections as a part of an execution of a single activity.

Advertisements

MetaVis Change Control and Release Manager

November 22, 2010

Product Overview

MetaVis Change Control and Release Manager for SharePoint (CCRM) is an off the shelf software tool that compares and promotes changes between two of more SharePoint environments.

Change Control and Release Manager provides a controllable and repeatable way to automate the following processes:

  • Propagate changes made in development environment to test one and then to production one
  • Bring back data collected in production environment to the test and to development ones
  • Distribute solutions from software vendor to multiple clients
  • Push updates to multiple SharePoint environments in the organization
  • Govern multiple SharePoint environments with centrally defined policies

Change Control and Release Manager employs several foundation tools to support business cases described above:

  • Live side-by-site compare tool that provides both high level and fine grained difference reports between SharePoint environments with the ability to drill down into the difference hierarchies and initiate object synchronization activities
  • A number graphical and background tools for objects copy activities that allow object copy on site collection, site, list and individual item levels
  • Activity management tool that allows defining , managing, grouping, execution and scheduling of the object compare, copy and synchronization activities defined by other tools

Change Control and Release Manager supports change management for the following SharePoint objects:

  • Sites, lists, libraries, fields, content types, content type and column groups
  • Folders, documents, document sets, pages, publishing pages, WIKIs and items
  • WEB Parts, list views and site welcome pages
  • Workflows
  • Term stores, term sets, terms and managed metadata columns
  • Users, groups, permission levels, permissions and permission inheritance

Concept and Terminology

Change Control and Release Manager implementation is based on a concept of activity. An activity is a unit of elementary operation like copy site, list or filtered group of items. Copy activity specifies source, destination and copy parameters.

Multiple activities may be grouped together and executed as a whole. For example, an activity may include a several list copy activities. Another example is an activity that copies site from development to QA and then copies QA site to the production environment. Yet another example is distribution of a single list to multiple different sites.

Change Control and Release Manager allows scheduling, managing, executing activity or groups of activities and viewing history of activity execution including the users who created, modified or executed the activity.

Activity history view allows browsing the activity execution log and other artifacts (like reports) of previous activity executions.

The activities themselves are based on the familiar MetaVis copy operations like copy site, list or items wizards.

.

Scheduling of activities may also utilize the full power of MetaVis Live Compare dialog.

Scheduling of activities could also be done using copy/paste or drag-and-drop operations in MetaVis Navigator View that reflects natural SharePoint object hierarchy.

The mission of Change Control and Release Manager is to provide an easy way to perform, monitor and audit large sets of repeatable operations that copy or synchronize multiple SharePoint environments.

MetaVis Cloud Classifier 2010 Preview

August 23, 2010

MetaVis Cloud Classifier 2010 is a SharePoint 2010 component that allows to assign field values to many selected documents located in SharePoint 2010 libraries at once. This component is available for any user of a SharePoint site for any library in the site collection where it is activated. It is completely integrated with SharePoint security model and embedded seamlessly into SharePoint WEB interface. In a sense, Cloud Classifier 2010 is like a standard Edit Properties dialog but it applies to all selected documents.

MetaVis Cloud Classifier 2010 allows SharePoint users to enhance documents metadata in an easy and organic way on a mass scale. This, in turn, improves documents find-ability, search, accessibility and navigation through SharePoint libraries.

MetaVis Cloud Classifier 2010 is very easy to use. First, select documents to tag in any place that allows document selection like library or list view WEB Part and click Classify button in SharePoint ribbon toolbar.

Then specify new field values for any of the fields that appear on the Classify screen and continue the wizard.

At the end, all values specified on the Classify screen will be applied to all documents selected in the list when Classify dialog was called.

This is just a basic use of MetaVis Cloud Classifier for SharePoint. In a more advanced scenario the user may change content types of the selected documents (remember, there might be many of them) and specify field values for this new content type:

Values for some fields could be copied from the other fields available in the existing metadata.

Coupled with SharePoint 2010 list navigation infrastructure and key filters MetaVis Cloud Classifier becomes a very powerful tool to perform metadata enhancement and data classification in SharePoint sites. Here, we select all documents pre-tagged with MK Region field contains China to tag them with new metadata, change their content type or add more values.

Please contact http://www.metavistech.com to receive more information about MetaVis Cloud Classifier 2010 and get a free trial.

Copy SharePoint 2010 Document Sets with MetaVis Migrator

July 20, 2010

Document Set is a new kind of objects supported by SharePoint 2010. The concept of Document Set has been around for quite a while in different content management systems. In Documentum they called it Virtual Document or, some of them, Assembly; in LiveLink they called it Compound Document. Microsoft brought this concept to SharePoint in its latest version. Document Set is a way to group related documents together. In a certain way it is like a folder but with several important differences. In some other way document set is like a document that consists of several other documents. Below is the picture of a Document Set with three documents inside and visible document set ribbon menu.

Document set is like a folder in a way that it can contain other documents and it could be located in a library together with other documents, folders or document sets. This is how document sets look in a list of documents.

Unlike folder, document set could be limited to contain only documents of certain content types. For example, we may create a document set content type in a list so that each document set instance will contain only Software Specifications and Project Plans.

Moreover, document sets, like regular documents, could have versions and could be sent to workflows as a single whole. For example, we can send a Car Loan Application document set with all its documents to an Approval workflow so that someone will check that all required documents are included in the set.

Latest version of MetaVis Migrator supports document sets in SharePoint 2010 sites as any other native SharePoint object. This is how document set looks in MetaVis interface. Copy it, paste it or drag it and drop to another list, site or server, alone or together with other documents or as a part of a list of a site.

Do not forget to select <Keep Original> Content Type on the properties page of the Copy Items Wizard if you do item level copy because there are several content types involved when you copy document sets.

Cool technique to copy SharePoint list with dependent content types to the right place to another site collection

June 4, 2010

This article discusses an interesting technique of copying SharePoint list with content types to different site collection. The task seems to be simple enough considering there are some tools on the market that can let user to grab a list and drag it and drop to the other site collection while performing some copy magic behind the scenes. Still, there is a place to think about before doing this drag and drop: list may have content types defined in the parent site, not in the same site where the list is defined.

Let’s, for the sake of simplicity, consider two sites: root site of the site collection (Publishing Portal in this case) and its sub-site (Mark’s Site).

Parent site Publishing Portal contains definitions for content types.

Sub-site Mark’s Site contains the list itself with all content types, views and content

We want to take this Repair Manuals list and copy/paste or drag-n-drop it to some other sub-site of some other site collection.

If we will do just that then the list will be created in our destination sub-site but all content types (that were before in the root site of the site collection) will be now created in the same destination sib-site. This is not good because someone probably created these Vehicle-based content types in the site collection root with the purpose to reuse it in different sub-sites of the same site collection. It would be nice to preserve this architecture in the destination site collection as well.

To do this we need to copy this list twice. First time, copy it to the root site of the destination site collection even if it ultimately should not go there. This time do not copy content, do not copy permissions, workflows or views related to the list. Just copy the list itself and all dependent content types. This way, all content types and fields will be automatically created together with the list in the right spot of the destination site collection. These content types and fields may be reused later on by other sites of this site collection. Here are options to copy just list with no content and other attributes like presented by MetaVis Migrator for SharePoint .

After this, delete the list from the root site of the destination site collection. All content types created in the root site will still be there because they are defined outside of the list.

As a last step, copy the same list again but this time – to the right sub-site of the destination site collection. It will create the list and reuse all content types from the root site created during the previous copy. This time, select all options for copy content, permissions and views on the copy list wizard screen.

This technique allows to preserve originally designed architecture of SharePoint site collection that involves complex taxonomies of site columns and content type hierarchies.

MetaVis Live Side-by-Side Site Compare

April 13, 2010

Earlier this week MetaVis for SharePoint added an experimental live side-by-side site compare function. Live compare allows user to select two SharePoint sites and compares the sites objects side-by-side in a single scrollable expandable tree view. The Compare View allows drilling down to sites, sub-sites, lists, content types, fields and object properties to see the difference between sites in a simple intuitive interface.

Moreover, the Compare View allows to select a difference record and to synchronize sites by copying selected objects. The object copy utilizes powerful MetaVis Migrator engine that enables copying sites, site hierarchies and lists.

We envision the following use cases for Live Compare functionality

  • Compare and synchronize site collections
  • Synchronize development, QA and production environments
  • Check the completeness of data migration
  • Quickly find a modified object property like “Major Versioning” enabled for some lists

To utilize MetaVis Live Compare connect to SharePoint sites, select them in MetaVis Navigator View like displayed on the picture below, right click and choose Live Compare menu option.