People have a few options for placing their FrameMaker documentation in version control. One option is to use the SharePoint CMS integration. What I don't understand is why someone would choose to use SharePoint for this. I have seen several points with complaints like "I have everything set up correctly but sharepoint still isn't working correctly for X reason...". Now there are business reasons why you may have to use SharePoint. For example, the organization you work for is all based on Sharepoint and they demand the use of SharePoint as a business requirement. However, if you have a choice, why not use subversion? I have been using it for years with my framemaker documentation. There are no configuration steps. Someone sets up the SVN repository and then you add the FrameMaker files. That's it; you are done. After that, SVN just works. However, the bottom line is that Sharepoint CMS sounds like a nightmare. I can personally attest there are almost no problems with using a SVN repository. From a technical standpoint, I have no idea what SharePoint could possibly provide that would make it worth the hassle it puts people through to do simple check ins and check outs. Joe
I understand your point however its just a Microsoft product that has collabaration with Adobe and we are using it and also Documentum , so if someone is not Happy with SP can use Documentum however its just a Personal choice that how you wanna do Controlling,either via Framemaker inbuilt CMS connection or your own,totally depends on you.
Its just to maintain the Industry measure across the globe that we always go with what is best in that particular industry ,thats why we have SP in it.
In my case, "business reasons" more or less nails it. Our company is implementing SharePoint and they're hoping I can use it for DITA. They'll entertain other options only if there are good reasons why we can't make SharePoint work for this. I've already started exploring the SharePoint API. Meanwhile, we have the SharePoint Connector working and we can check files in and out -- it's not that difficult.
I've heard about Subversion, but I understand that it's mainly a source-control application. I have no shortage of those to choose from; our company already uses MKS and TFS. (In fact I'm using MKS to store one of my DITA projects.) SharePoint has an edge over them because it allows me to associate custom metadata with a library (say "topic type" or "audience"), complete with a list of fixed values like "concept" and "task" for our authors to choose from. I'm not sure if Subversion offers similar functionality.
Where all of them fall down is in the area Nakshatra mentions -- dependency management. If I want to rename a file, or replace a Windows7 screenshot with a Windows8 screenshot that has a different file name, or I want to know everywhere a conref is used, or want an alert when someone changes the conref, I need an underlying database to make the file management system "DITA-aware."
I was all set to create such a database for our SharePoint implementation, along with a user interface -- very gradually, in small steps over a long time. FM's "FMDependency" field presents an unexpected complication for this plan, and I'm still absorbing that.
If Subversion is "DITA-aware" or has promising open-source plugins to make it so, I'm interested. Otherwise I still have to develop a database and UI, and in my case, I might as well try to do it with SharePoint.
Europe, Middle East and Africa