SharePoint 2010 document IDs with file shares

I'm aware that that SharePoint 2010 includes a feature for assigning document IDs to files within SharePoint site collections:

http://blogs.msdn.com/b/ecm/archive/2011/10/12/document-id-in-sharepoint-server-2010.aspx

What I'm wondering is if SharePoint also applies document IDs to file share content sources that have been added as part of the SharePoint search crawl.  In SharePoint 2007 we have users that create links pointing to files on a network file share.  Occasionally, a file gets renamed or moved and ultimately breaks the SharePoint link.  Do SharePoint 2010 document IDs apply in this scenario and provide persistent links in SharePoint for file shares?
LVL 1
curt2000Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

colly92002Commented:
As I understand it, Document IDs are a site collection feature, and so can only apply to site content.  The fact that you can use search to index shares is not really relevant (you are simply building an index of the data source).  The index will of course update when it crawls, so this will always point to "live" content.

Why not migrate your shares into Sharepoint?
0
Jamie McAllister MVPSharePoint ConsultantCommented:
As colly92002 says, Document IDs are not going to be a solution to your users custom links - they operate on content in SharePoint.

A broken links checker might help you, but it's no silver bullet as this debate shows;

http://sharepoint.stackexchange.com/questions/3812/is-there-a-link-checker-for-sharepoint-2010

The OOTB checker works for links within SharePoint, and the suggested Mavention tool only works on a per page basis.

If you need to make a case for migrating fileshare content to SharePoint I made a few points here that might help;

http://the-north.com/sharepoint/post/2009/11/26/Moving-from-File-Shares-to-Sharepoint-Lists.aspx

This was written with MOSS 2007 in mind. The only update I'd make is that the Document Management features in SharePoint 2010 are richer than they were in 2007 - hopefully bolstering the case.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
curt2000Author Commented:
Excellent.  Thank you both for answering my question and confirming my suspicions.  Now I can plan our SharePoint 2010 migration project accordingly.  

I always felt that accessing documents on file shares was much faster/desirable than going through an HTTP server to access documents (our SharePoint 2007 setup is slow I guess).  I was hoping document IDs would provide a solution for broken links between SharePoint and file shares, but Jamie's article on the topic was helpful for getting beyond the purely "hierarchical navigation" organization strategy.

And thanks for the link checker program too!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.