Posts Tagged ‘library’

Bulk Uploading content from File Shares using a Spreadsheet for Metadata

February 3, 2011

One of the first features that we added to our Classifier product, which is designed to bulk tag SharePoint content, was the ability to migrate file system content into SharePoint. Customers wanted MetaVis to enhance the usability of SharePoint by adding the ability to upload files and classify them at the same time while also enriching the file metadata and maintaining the created and modified properties. In the past few years, we have continued to add features to Classifier including:

  • the ability to map NTFS metadata from a file system such as folder names (which is the original way to tag files) into SharePoint fields;
  • the ability to apply SharePoint 2010 managed metadata;
  • the ability to unravel the folder hierarchy for those users that want to maintain their content in SharePoint without using folders; and
  • many more small conveniences or other features that fill gaps left by SharePoint 2007 and SharePoint 2010.

One commonly requested feature that kept coming up (and one that we have resisted to implement) was the ability to use a spreadsheet for file import. The idea seems straight forward. Create a spreadsheet that catalogs you files. Let users input field values into the spreadsheet. Then import the files using the spreadsheet for your metadata.

My past experience, inspired the MetaVis team to think of ways we could improve upon the process and satisfy the market demand for using a spreadsheet/CSV file that is simple and effective. Here is what the MetaVis team came up with:

Begin by generating the spreadsheet from the target list

Step 1) Start by identifying the files and folders that you want to import into SharePoint. There are two ways to do this. The first way is to expand and navigate through the My System area in the product. If you double click on a folder or drive, the contents will be displayed in the Contents area. You may drag-and-drop or copy/paste from My System or Contents areas directly to the destination. Alternatively, MetaVis provides the same capabilities directly from Windows Explorer

Step 2) After you have selected the content and dragged/copied it to your SharePoint destination, a familiar wizard will be displayed. This is the same wizard that is used to copy SharePoint content from one place to another. The first window will confirm the destination

Step 3) The second window will give you an ability to apply metadata values. It is a good idea to take advantage of this feature and apply as many metadata values as since all the data is validated against SharePoint. There are many capabilities for intelligent and auto tagging available including mapping to NTFS values such as folder names, file names, owners, etc.; or to select values directly from SharePoint managed metadata, choice and lookup lists.



Step 4) The final screen of the wizard has a new check box towards the bottom of the page. Selecting the Create CSV File for uploading files option will generate a comma separated values file compatible with Excel or any text editing software

Step 5) Although the file content may vary based on selected metadata and options the basic structure will always have the following layout:


Source File

SharePoint File Name


Field 1

Field 2

Created By

Created At

Modified By

Modified At



Your Value

Your Value

Your Value

File Owner

Created Date

File Owner

Modified Date



The layout must notbe changed or otherwise the imported file will not be recognized. However, the content may be edited to your preferences. Remember that any values that are modified or edited must be valid to SharePoint. Otherwise they will be ignored or an error will be generated.

Step 6) Once you finish working with your spreadsheet, you are ready for the last step in the process. The ability to Upload Files Using CSV is available at any library or folder right-click menu. Identify the destination for your files and select this option. In theory, the same destination as was chosen in step 1 should be used, but there is no such restriction. So, if you have more than one library into which you want to import your files and they have the same or similar metadata structure, the.csv file can be reused

Step 7) Next the Open File for Import screen will be generated. Enter the location of your .csv file

Step 8 ) The contents of the file will be loaded in the space provided below. You may stretch and scroll the screen to view the contents.

Step 9) You may check individual items or the Check All button at the bottom to select everything. In addition if you are using a custom character set, select it in the provided field.

Step 10) To start the import, press the Finish button.

In ten easy steps you can bulk upload content from File Shares using a spreadsheet for metadata. Give it a try and let us know what you think. Any and all feedback is always appreciated and welcomed!

Maintaining Created / Modified properties while copying or tagging documents in SharePoint

December 18, 2009

Each SharePoint item and document has special Created By, Created At, Modified By and Modified At properties that can be seen on the item’s View Properties screen. These properties are not editable with SharePoint GUI but sometimes it is desirable to keep these properties while copying document from one location to the other one, uploading a file from file system or re-classifying the document with new content type or field values.

Below are some typical cases that would benefit from maintaining original values for these “core” properties at the time of moving, copying or uploading an item:

  • Created At property could be used to enforce document retention policy. During its life-cycle document may travel from file system to a list in SharePoint and to an other SharePoint site. In this case it would be nice to keep the created date of the original document instead of the date of moving to its last location.
  • Created By property could be used in a navigational list view with grouping that include original document author. Unless this property will be preserved during document copy, the document would not be found in the author category it belongs.
  • Modified At property could be an indicator of items that have been recently changed. The change would trigger a special workflow for an item or cause a notification. In case of maintenance (not business related) changes such business related activities should be waved. These maintenance changes may include mass enhancement of metadata of simple copying items to another location.

MetaVis Classifier and Migrator products optionally allow user to maintain Created By, Created At, Modified By and Modified At properties during item tag, copy or file upload to SharePoint. To enable this functionality a special product called MetaVis Core Properties Service has to be installed on the destination SharePoint server – the one where these properties values should be maintained.

After MetaVis Core Properties Service has been installed on the destination SharePoint server, MetaVis Classifier and Migrator products detect it automatically during items copy. In this case MetaVis displays all four created / modified properties on the Copy Wizard Properties screen. By default these properties are set up to keep original value they had on the source item but there are several other possibilities listed below for defining their values during items copy or tag. Note that any of these cases could be applied to any of four core properties independently.

  • Copy value to the property from the same property of the source item (Create At to Create At, Modified By to Modified By, etc). This is the default choice on the Properties screen of the Copy Wizard. This choice maintains the original created / modified property value as it was in the source item whether it was located in other SharePoint site or on file system.
  • Copy value to the property from the other property of the source item. This option allows to set Modified At field to the value of the Created At field of the original item or to copy a value from a custom Person or Group column to a Created By field.
  • Let SharePoint set this property. This option does not copy any values. After the item copy, Created At and Modified At properties of a newly copied items will be set to the current time, Created By and Modified By fields will be set to the current user. After tag or copy to the new version only Modified properties would be set to current time and user.
  • Set certain value for this property. A user for Created By or Modified By fields could be selected from the list of users. Date and time for Created At or Modified At fields could be selected using calendar control.

When bulk list or site copy is performed instead of item level copy MetaVis Migrator will preserve all four created / modified properties from the original source item. MetaVis Migrator will also preserve all four created / modified properties if “Keep Original Content Type” option is selected on the Properties screen of the Copy / Tag Wizard during item level copy.

These flexible choices allow to plan each copy or tag process with respect to the intended use of a document or an item during its life-cycle.