I'm using FM10 (with DITA-FMx) and SharePoint 2010. We're using SharePoint as a DITA file repository.
Given a document library created in SharePoint; a DITA map; and a Topics folder containing the topics referenced in the map:
- If I upload the DITA map from the FM SharePoint Connector, the Topics folder is created and all the topic files are uploaded automatically. Then, when I Check Out and Edit the map and select "Checkout all dependent files," all the dependent files (the topics) are checked out successfully. Other users on other machines can also check out the map and its dependents successfully.
- On the other hand, if I copy the map, the Topics folder, and the folder contents to the document library using a Windows Explorer connection or a webdav-mapped drive, then, when I Check Out and Edit the map from SharePoint Connector, the dependent files are not checked out successfully. In the map (as viewed in DITA-FMx), the topic files are all shown as "Not found," and in the C:\users\[etc] directory where FM keeps its SharePoint Connector files, the topic files are not created.
Why is there a difference? Is there a way I can use webdav or Windows Explorer to upload a project to SharePoint, and still use the FM SharePoint Connector to open the files successfully?
To answer your question, it's important to understand that Sharepoint, in itself, is not intelligent enough to handle the external dependencies associated with composite documents, say a DITAMap, or for that matter individual file with dependencies. And so, to achieve this integration FrameMaker uses the file metadata on the CMS to build and store these relationships.
Therefore if you do not migrate your fileset from within FrameMaker, there is no way that these relationships can be created/maintained on the Sharepoint server.
PS: If you really want to head in this direction you can explore the Sharepoint APIs to build these dependencies yourself, but it will be a daunting and an iterative task. Not advised.
Europe, Middle East and Africa