FC.MetadataExtractor 3.2 released for SharePoint 2010


On the heels of the 2.3 release (for SharePoint 2007), comes the announcement for the 3.2 release for SharePoint 2010.

All the goodies introduced in the 2.3 release have also found their way into the 3.2 release.

Of course we didn't stop there, and implemented several new features that will make it even easier for you to extract the right metadata.

The Highlights of this latest release are:
  • Better looking Thumbnails
  • Thumbnails everywhere
  • Thumbnails and Metadata Extraction for RAW, PSD, or DNG files
  • Metadata Extraction from images in folders and their subfolders
  • Full Control over all metadata extraction processes running in the background
  • Writing Metadata back to the image
  • More, and improved, Default Mappings
  • New "Standard Mappings"
  • Adding and Editing a Field Mapping - Simplified!

 

Better looking Thumbnails

This latest release has a new component called "Unified Thumbnail". One of its most prominent features is that it uses the color profile stored in the image to provide a better thumbnail quality. See for yourself:

 

SharePoint:

FC.MetadataExtractor:

 SharePoint Thumbnail  FC.MetadataExtractor Thumbnail

 

Thumbnails everywhere

By default, SharePoint does not create thumbnails in any document library other than the Assets and the Pictures library. SharePoint also does not create thumbnails whenever a file does not have the windows filetype extension in the filename.


The Unified Thumbnail enables thumbnails in all kinds of document libraries. Even in the Assets and Pictures libraries it can add value by creating thumbnails for formats not supported by SharePoint.

 

Unified Thumbnail

 

Thumbnails and Metadata Extraction for RAW, PSD, or DNG files

SharePoint only creates thumbnails for a few formats, like jpg and png. Other formats, e.g. RAW formats like CR2 or NEF, or even PSD images are not supported by SharePoint.


The Unified Thumbnail provides thumbnails for all formats for which a WIC codec has been installed. Such codecs might be available from your camera vendor, but there are also low-cost codecs available from vendors like Ardfry (PSD, DNG) and FastPictureViewer (wide range of RAW codecs).

Keep in mind that 64-bit (x64) codecs are required for use with SharePoint 2010.

 

Metadata Extraction from images in folders and their subfolders

If you have a document library with images organized in folders, the images in this library can now be processed by the FC.MetadataExtractor in one simple step: Select the top-level folders and start the "Manual Extraction". The 3.2 release will automatically parse through all folders and sub-folders to extract the thumbnail and metadata from all images in that library.

 

Full Control over all metadata extraction processes running in the background

Extracting metadata and creating thumbnails for a large number of images can be a lengthy operation. This process is conducted in the background to allow the user to continue to work. Until now, whether any such process is active and what its progress is has been somewhat invisible. This is why we introduced the "Extraction Control", which provides transparency over any such process running in the site, and also enables the site collection administrator to cancel any of these processes.


Background Extraction Processes

 

Writing Metadata back to the image

SharePoint 2010 added the functionality to some SharePoint columns to write metadata back to the image. We've tested this functionality and have slightly modified our Default Mappings to include the following columns:

  • Copyright (previously: CopyrightNotice was used)
  • Keywords
  • Author (previously: Photographer was used)
  • Date Picture Taken
  • Comments
  • Subject

 

Note: The Comments and Subject metadata is written back to the image, but not to the typical location in the file, so it might not show in your image editing application.

 

The standard SharePoint columns "Title" and "Name" also write back to the image.

 

More and Improved Default Mappings

Several Field Mappings have been added and many of the previously existing mappings have been enhanced, e.g. by explicit access to png and gif fields. For a complete list of the current Default Mappings please see the product manual which is included with the demo download from our website.

 

New "Standard Mappings"

Metadata mappings configured for one library can now easily be copied to other libraries in the site collection using the new commands:

 

Standard Mappings

 

Adding and Editing a Field Mapping - Simplified!

Any existing Field Mapping can now be entirely modified later on. Gone are the days when this sometimes required creating a new field mapping. Plus, a link is now provided to create a missing column in the library and several checks are performed automatically to avoid creating an invalid mapping.

 

Go Get It!

The new release is already available as a download from our website. Go give it a spin and see if you like the new and improved features!


Published: Jul-06-11 | 0 Comments | Link to this post

FC.MetadataExtractor 2.3 released

I've been looking forward to announcing this major release, as it holds a good number of new features and usability improvements.
 
The highlights for me are:
- Extended file format support
- Much improved ease of use around configuring and applying metadata mappings
- Fixing the page redirect after manually starting the extraction of metadata for images already in the library
 
Extended file format support
In addition to the existing standard image formats like JPG, TIF or GIF etc., the FC.MetadataExtractor now leverages ALL WIC-compatible codecs that are installed on the SharePoint server. This potentially allows to extract metadata from various RAW file types (e.g. CR2 and NEF), as well as PSD or even DNG files.
Be aware that some of these codecs are freely available (e.g. many camera manufacturers provide the codec for their RAW format for free), while others cost a little bit of money.
 
 
Improvements of Metadata Mappings Configuration
First off, it is now possible to change the Field definition at any time, just like the choice of the list column the metadata should be written to. (I know, we should have done it this way a looong time ago)
 
Also, it is now possible to save the Metadata Mappings configured for one library as the "Standard Mappings" for the Site Collection, after which these mappings can then be easily added to other libraries as well.
 
Then, we've updated the default mappings and columns to include Fields which have become more popular over the last months. E.g. Latitude and Longitude are now default columns.
 
Several of the default columns of type Text are now Note fields in the library rather than Single Line Text fields, as we've seen more information being stored in them. Several of our customers found out that SharePoint is not "forgiving" if you try to store excessive amounts of text into a Text column. In such case SharePoint will actually update NONE of the fields of the item.
 
We've continued improving and completing the metadata access as much as possible. E.g. this time we've added better formatting of RATIONAL values and arrays of RATIONAL. I think by now we have a very solid metadata access implementation, even on older Operating Systems like Windows 2003R2, where the WIC functionality is still very limited.
 
Also please note that Microsoft has improved their documentation on the WIC (here and here), which might be helpful for you to determine  the right access string for the metadata Field.
 
 
Fixing the page redirect
We've had that request for quite some time, but the redirect to the right page view or paged view of a folder in the library was a bit complex to implement. I am very happy that we finally got this covered as I think it is a big nuisance for a user to manually return to a specific page view of the library.
 
The demo is already up on our website, so go get it and give it a test drive.
 
The Upgrade to version 2.3 is FREE for existing customers.
Enjoy!

Published: May-02-11 | 0 Comments | Link to this post

Accessing Location metadata using WIC - Windows Imaging Components

A customer just asked me how to retrieve the "City" metadata using the WIC. It's actually straight forward to pull that out of the IPTC information in most cases, as that is where Photoshop puts it when using the IPTC tab's "Sub-Location section, or the Origin tab.
 
app13/irb/8bimiptc/iptc/City
 
The "Country" is a little bit more tricky because the name of the resource contains a forward slash: ""Country/Primary Location Name"
 
/app13/irb/8bimiptc/iptc/Country\/Primary Location Name
 
Of course, one shouldn't confuse that "City" with the creator's "City" metadata,, which can be found here:
 
/xmp/CreatorContactInfo/CiAdrCity
 
HTH!

Published: Jan-22-11 | 0 Comments | Link to this post

More "Site Assets" issues

Haileselassi!
 
While we're finishing the port of our FC.ImageSearch product to SharePoint 2010 we're coming across a number of flaws with the search result mechanism and especially the "Site Assets" library, which is a new feature in the commercial version of SharePoint 2010.
 
What's wrong with this picture?
 
Site Assets search result data 
 
sitename
Well, the "Site Assets" part (marked in yellow in the screenshot above) is not a sub site but in fact the name of the library. So, the real sitename should be http://2k8r2x64sp10.
 
What's worse is that if you have a search result that is stored within a folder of a library then even the folder name will be concatenated to the sitename!
 
contentclass
As written in the previous blog post, the Site Assets library has a BaseTemplate and RegistrationID of "851". Well, that lack of better naming exists in the search result as well: while the Picture library has a proper contentclass of type "STS_ListItem_PictureLibrary", the Site Assets library is of contentclass "STS_ListItem_851".
 
picturethumbnailurl
Well, as you can see there are no thumbnails available for the images in a Site Assets library. Of course, that is wrong: as you probably noted, the Site Assets library absolutely contains the usual thumbnail and web preview images in the "_t" and "_w" folders. The links just don't get carried over to the search result.
 
 

Published: Oct-24-10 | 0 Comments | Link to this post

Leverage the FREE Windows TIFF iFilter for OCR in SharePoint

I knew about the TIFF iFilter available in Windows 2008R2 and its OCR capabilities, but I had not had the time to try it out until very recently when it became a priority as a customer requested it.
 
The setup for it is very SIMPLE and well described in John Liu's blog post. It consists of no more than two essential steps: activating the TIFF iFilter Windows Feature and to configure the OCR Group Policy properties.
 
I might want to add a couple of things to John's description though:
 
1) You should also configure the option "Select OCR languages from a code page".
 
2) You do NOT need to restart your server: simply restart the SharePoint Search services and then execute an iisreset.
 
3) You only need to start a "Full Crawl" if you want to reindex TIFF files that are already in SharePoint. All TIFF files uploaded AFTER the iisreset will be indexed automatically.
 
Of course you need to consider the amount of text being added to the general search index file. However, the upside of searching on all the scanned documents' text is certainly quite obvious.

Published: Sep-20-10 | 0 Comments | Link to this post

FC.MetadataExtractor released for SharePoint 2010

A few days ago we released our first product for the new SharePoint 2010 platform: FC.MetadataExtractor 3.0
 
By far the biggest improvement in SharePoint 2010, in regards to this new release of our product, is the ability to better control the asynchronous ItemAdded event receiver. Given the positive feedback at the SharePoint 2010 conference when Microsoft announced the addition of such a synchronous ItemAdded event, quite a number of people must have encountered that problem.
 
Recap: in SharePoint 2007, the ItemAdded event fires asynchonously and so does the thread that brings up the EditForm.aspx with the properties of the newly created item. This of course creates a collision if both threads then try to modify that same item. The only way out of this issue was to provide a custom EditForm.aspx page that would wait for the ItemAdded event receiver to finish before the EditForm.aspx would load and access the item.
 
In SharePoint 2010 the ItemAdded event receiver can now be configured to either fire synchronously or asynchronously and also be given a sequence number. This eliminates the need for a custom EditForm and any manual synchronization and allowed a much "cleaner" solution with the new product release.
 
On the user interface front, the Ribbon does take a bit to get used to, both for programmers and users. I do think though that accessing the Ribbon is easier for many users than having to search through several popup menus for a certain command.
 
FC.MetadataExtractor for SharePoint 2010
 
The ability to have client-side ECMAscript code and the new Notification elements in the user interface is definitely a great step forward. We made use of it for the manual metadata extraction that now happens asynchronously at the server while the user can continue to work in the browser.

Published: Jun-24-10 | 0 Comments | Link to this post

FC.ImageSearch released!

I am very happy that we've shipped this product, because I believe that it will mean a big difference for everyone who searches for images in SharePoint. It's not just about the proper layout of thumbnails on the search result page, but also about having the right links with the search results which makes the search experience so much more powerful. And of course, having thumbnails for images stored in any kind of library, or even file shares, is great too.
 
FC.ImageSearch result page
 
My favorite part of the solution though, is the streamlined view of all the search-related administrative information, and the ability to configure the search in one place rather than manually modifying properties scattered across the Central Administration and the library properties. Not to speak about the properties in the advanced search page and the core search result page. It now, literally, takes only seconds to add a library column as a Managed Property, or to add it right away also as a search criteria for the Advanced page.
 
Well, releasing a product is also always the right time to share some credits, which I am happy to do here:
 
Matthew McDermott's 4 part series on configuring image search results somewhat inspired us to turn his suggestion into a real product.
 
 
And of course, the late Patrick Tisseghem deserves a lot of credit too for his book, the webcasts and articles he provided. Patrick, you're missed.

Published: May-08-10 | 2 Comments | Link to this post

Next Product up: FC.ImageSearchResults

Right on the heels of our FC.MetadataExtractor 2.0 release shortly before Christmas we're working hard on getting a fun product out the door: FC.ImageSearchResults. It'll probably be another couple of weeks before we hit beta 1, but I thought I should already mention it here.
 
All the metadata that can be unleashed by the FC.MetadataExtractor product will be available to search on if the FC.ImageSearchResults solution is installed. And what's best, the solution comes with a custom searchresult page that displays those images nicely with thumbnails and metadata that makes sense for images. I'll blog more about this as we get closer to the public beta release.
 
As always with our product efforts we're aiming to support both MOSS (the commercial product) as well as WSS 3. This time I am especially happy to tell that there will also be support for a free version of SharePoint: while search in WSS 3 simply sucks, the Search Server Express 2008 (SSX) product (that simply can be installed "over" an existing WSS 3 installation) has all the bells and whistles to serve as the basis for our search solution.
 
If you run WSS 3 and haven't looked at SSX yet ...I highly recommend you do so ASAP!
 
The object model of the libraries that get installed with the SSX "upgrade" for WSS 3 have everything we need for our solution. Even the Search user interface that is added to the Central Administration is quite nice. However, there was one thing that was missing: a link to the page to manage the so-called "Shared Scopes". Our solution installs a Share Scope called "All Images" that allows to search across the entire farm and while we do that programmatically we of course prefer it to be visible to the administrator, so what is installed is transparent.
 
Well, the respective admin page for managing the scopes is actually installed. Just the link is missing. So you can get to that page simply using this link:
 
http://<server name>:<central admin port>/ssp/admin/_layouts/viewscopesssp.aspx?mode=ssp
 
View Scopes

Published: Jan-16-10 | 0 Comments | Link to this post

SharePoint DAM: Versioning Metadata

As we've just released the 2.0 version of our FC.MetadataExtractor product I thought I should catch up with some blog postings on DAM functionality in SharePoint.
 
One of the great things that come with SharePoint 2007 and WSS 3 is that you can keep track not only of the different versions of an image but also of its metadata. This is extremely helpful as entering metadata in a corporate environment is usually done over multiple rounds and maybe even involves several contributors.
 
All you need to do to activate versioning of metadata is to enable Versioning in the Site Settings:
 
Versioning Metadata
 
Once that is enabled you can either create a new version by uploading a new version of the image which includes new metadata, or by editing the metadata directly in SharePoint.
 
The Version history is now available via the item's context menu and the metadata trail can be seen in the screenshot below:
 
Versioned Metadata
 
This is just one example of the great base-level functionality SharePoint 2007 / WSS 3 include that can be applied in many scenarios, but is especially useful for metadata-heavy applications like DAM.

Published: Dec-23-09 | 0 Comments | Link to this post

FC.MetadataExtractor 2.0 Launch

It's been quite a busy time lately, as we were zeroing in on the 2.0 release of our FC.MetadataExtractor solution, and I have to say that the good old 80/20 rule certainly still applies (the last 20% of the work takes 80% of the time).
 
Just to give a quick overview: The FC. MetadataExtractor reads metadata from images - either on upload, or triggered manually - and stores it in the Sharepoint columns.
 
As the SharePoint custom document parser interface turned out to not be available for the main image formats we had to use Event Receivers. However, those also turned out to be quite inadequate, e.g. as the ItemUpdated receiver is asynchronous and interferes with the EditForm that comes up when someone uploads a single image. Hristo Pavlov had a good suggestion on how to solve that one problem, but it still leaves a lot of questions on how to wrap all this customization into a single feature, which is to be installed.
 
And beyond that there were many more individual problems attached to the different ways to upload or move images to a SharePoint library. Some of them are related to IIS and SharePoint settings in general, like for uploading large image files. I'll do a separate post on this once we're through with the release.
 
At this point I also want to thank our beta testers. They are still the best source of inspiration and guidance!!

Published: Dec-11-09 | 0 Comments | Link to this post
 Next >>