Content Importer general access for authors

Our team is responsible for our company's Tridion Docs instance (v15.2). We've been using TD for 10 years. We find that Content Importer works great for translated content. However, it is more error-prone for English content. In fact, when we outsource conversion to DITA, the vendor always chooses to avoid Content Importer, instead opting for their custom methods instead. Aside from migrations, English imports are rarely requested by our authors. When they are needed, our support team does them for the authors who request them. However, the use cases are growing and there is more of a demand for English content imports.

  • Do you generally allow access to Content Importer for your authors?
  • If so, what risks has that presented?
  • What are your general best practices for authors using Content Importer?
  • Or do you generally limit it only to support roles?

Thanks for your perspective. 

emoji
  • Hi Stacey - a couple of things. At FICO, only our administrators perform imports. We always import into an "Import" folder (with subfolders for each project) so the writers can check the imported files before moving them into the main repo. (If you are importing updated versions of topics that are already in the repo, this won't work because the object will be overwritten at its current location.) I hope this helps.

    emoji