How to handle very Large document (1000 of pages) in SharePoint

%3CLINGO-SUB%20id%3D%22lingo-sub-297462%22%20slang%3D%22en-US%22%3EHow%20to%20handle%20very%20Large%20document%20(1000%20of%20pages)%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297462%22%20slang%3D%22en-US%22%3E%3CH1%20id%3D%22toc-hId-1849618913%22%20id%3D%22toc-hId-1849618913%22%3ESharePoint%20Solution%20for%20very%20large%20documents%3C%2FH1%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20its%20a%20simple%20solution%20and%20I%20have%20presented%20to%20some%20of%20my%20customer%2C%20Just%20wanted%20to%20get%20your%20opinion%20that%20is%20there%20a%20better%20way%20to%20handle%20these%20large%20document%20with%20SharePoint%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20feel%20free%20to%20comment%20on%20it%20%2C%20I%20would%20like%20to%20see%20if%20there%20are%20better%20option%20leveraging%20any%20other%20apps%20with%20in%20MS%20365%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20slide%20from%20my%20Solution%20presentation.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F62125iE94905FACD11C68B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22TTT_Wiki1.jpg%22%20title%3D%22TTT_Wiki1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EWhen%20you%20have%20a%20large%20set%20of%20documents%20which%20are%20hundreds%20of%20thousands%20of%20pages%2C%20such%20as%20Product%20Manuals%2C%20corporate%20policies%2C%20Keying%20instructions%20files%20etc%2C...%3C%2FP%3E%3CP%3EHere%20are%20some%20customer%20use%20cases%2F%20pain%20points%20with%20respect%20to%20handling%20large%20documents%20within%20their%20corporate%20content%20management%20space.%3C%2FP%3E%3CUL%3E%3CLI%3EA%20single%20document%20which%20has%20several%20pages%20(1000%2B%20pages)%3C%2FLI%3E%3CLI%3EDocument%20that%20are%20edited%20or%20updated%20on%20a%20regular%20basis.%3C%2FLI%3E%3CLI%3EVersioning%20of%20the%20document%20continues%20to%20exist%20for%20audit%20and%20as%20a%20reference%3C%2FLI%3E%3CLI%3EOnly%20particular%20pages%20of%20the%20document%20to%20be%20shared%20with%20particular%20users%20and%20not%20the%20whole%20document%3C%2FLI%3E%3CLI%3EExternal%20sharing%20%26amp%3B%20editing%3C%2FLI%3E%3CLI%3EEditing%20and%20referencing%26nbsp%3Bother%20child%20document%20references%20within%20a%20document%26nbsp%3B%3C%2FLI%3E%3C%2FUL%3E%3CP%3EIn%20such%20cases%20it%20is%20not%20advisable%20or%20even%20feasible%20to%20keep%20these%20large%20files%20in%20One%20Drive%20or%20SharePoint%20library.%20Splitting%20the%20files%20into%20smaller%20chunks%20and%20uploading%20is%20not%20an%20option%20either.%3C%2FP%3E%3CP%3EOne%20solution%20that%20I%20implemented%20for%20one%20of%20our%20clients%20is%20to%20transform%20these%20large%20documents%20into%20SharePoint%20Wiki%20pages%20and%20load%20them%20into%20Wiki%20libraries.%20SharePoint%20Wiki%20pages%20are%20widely%20used%20in%20organizations%20and%20easy%20to%20create%2Cedit%2C%20share%20information%20and%20collaborate%20with%20others.%20They%20are%20very%20intuitive%20to%20create%20and%20use%20and%20thus%20easy%20for%20the%20users%20to%20adopt%20and%20maintain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH3%20id%3D%22toc-hId--1095565058%22%20id%3D%22toc-hId--1095565058%22%3ESolution%20diagram%3C%2FH3%3E%3CP%3E%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20827px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F62127i2D2A69A2B5C0B291%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22WikiMigration.jpg%22%20title%3D%22WikiMigration.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH3%20id%3D%22toc-hId-647245277%22%20id%3D%22toc-hId-647245277%22%3EBenefits%20of%20migrating%20to%20wiki%20pages%3A%3C%2FH3%3E%3CUL%3E%3CLI%3EAbility%20to%20edit%20and%20publish%20individual%20pages%20and%20not%20the%20whole%20document%20(that%20has%201000%2B%20pages)%20every%20time%20a%20page%20is%20edited.%3C%2FLI%3E%3CLI%3EMinor%20versions%20and%20comments%20%3A%20Versions%20are%20created%20only%20for%20the%20edited%20pages%20and%20tracking%20the%20version%20is%20easy%20and%20color%20coded.%3C%2FLI%3E%3CLI%3ETable%20of%20contents%20%26amp%3B%20easy%20navigation%20to%20the%20pages%3A%20Relevant%20pages%20are%20grouped%20together%20through%20table%20of%20contents%20and%20quick%20link%20references%20to%20other%20related%20materials%20can%20be%20maintained%3C%2FLI%3E%3CLI%3EEmbedding%20diagrams%2C%20reports%2C%20tables%2C%20lists%2C%20pictures%20and%20videos%20is%20easy.%20These%20can%20be%20simply%20loaded%20from%20the%20managed%20library.%3C%2FLI%3E%3CLI%3EAbility%20to%20save%20Page%20drafts%20and%20enforce%20approval%20process%20on%20publishing%3C%2FLI%3E%3CLI%3EPage%20rating%20and%20bookmarks%3C%2FLI%3E%3CLI%3EIn-page%20metadata%20and%20intuitive%20search%20across%20pages%3C%2FLI%3E%3C%2FUL%3E%3CH3%20id%3D%22toc-hId--1904911684%22%20id%3D%22toc-hId--1904911684%22%3ESummary%3A%3C%2FH3%3E%3CP%3EHandling%20large%20electronic%20documents%20and%20other%20content%20can%20be%20cumbersome%20and%20time%20consuming%20for%20businesses%2C%20even%20though%20it%20is%20not%20as%20hard%20as%20maintaining%20a%20large%20volume%20of%20paper%20piles.%20SharePoint%20wiki%20pages%20and%20Enterprise%20Wiki%20sites%20are%20a%20simple%20yet%20effective%20solution%20that%20can%20address%20majority%20of%20these%20issues.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-297462%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOneDrive%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPermissions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESites%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298318%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20handle%20very%20Large%20document%20(1000%20of%20pages)%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298318%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20It%20is%20%2C%20just%20better%20than%20copy%20%26amp%3B%20pasting%20manually%20%3A)%3C%2Fimg%3E%20that%20was%20one%20issue%20what%20we%20faced.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298317%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20handle%20very%20Large%20document%20(1000%20of%20pages)%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298317%22%20slang%3D%22en-US%22%3E%3CP%3EOk!%20Thanks..I%20guess%20this%20will%20take%20some%20time%20for%20a%20large%20library%26nbsp%3B%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298311%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20handle%20very%20Large%20document%20(1000%20of%20pages)%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298311%22%20slang%3D%22en-US%22%3EHow%20did%20I%20miss%20it%20%3A)..%3CBR%20%2F%3EI%20have%20used%20Word%20to%20Wiki%20Online%20app.%20its%20a%20nice%20tool%20..%20we%20tried%20first%20and%20liked%2C%20the%20paid%20version%20is%20really%20good.%20Here%20is%20the%20link%20to%20the%20tool.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fappsource.microsoft.com%2Fen-us%2Fproduct%2Foffice%2FWA104379573%3Ftab%3DOverview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fappsource.microsoft.com%2Fen-us%2Fproduct%2Foffice%2FWA104379573%3Ftab%3DOverview%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297785%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20handle%20very%20Large%20document%20(1000%20of%20pages)%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297785%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20question%20as%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E.%20Last%20time%20I%20tried%20to%20do%20something%20like%20this%20there%20were%20many%20limitation%20in%20the%20formatting%20of%20wiki%20pages%2C%20has%20that%20been%20improved%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297755%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20handle%20very%20Large%20document%20(1000%20of%20pages)%20in%20SharePoint%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297755%22%20slang%3D%22en-US%22%3EGood%20article!%20How%20do%20you%20perform%20this%20migration%20to%20wikipages%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E
Super Contributor

SharePoint Solution for very large documents

 

I know its a simple solution and I have presented to some of my customer, Just wanted to get your opinion that is there a better way to handle these large document with SharePoint?

 

Please feel free to comment on it , I would like to see if there are better option leveraging any other apps with in MS 365 

 

A slide from my Solution presentation.

TTT_Wiki1.jpg

When you have a large set of documents which are hundreds of thousands of pages, such as Product Manuals, corporate policies, Keying instructions files etc,...

Here are some customer use cases/ pain points with respect to handling large documents within their corporate content management space.

  • A single document which has several pages (1000+ pages)
  • Document that are edited or updated on a regular basis.
  • Versioning of the document continues to exist for audit and as a reference
  • Only particular pages of the document to be shared with particular users and not the whole document
  • External sharing & editing
  • Editing and referencing other child document references within a document 

In such cases it is not advisable or even feasible to keep these large files in One Drive or SharePoint library. Splitting the files into smaller chunks and uploading is not an option either.

One solution that I implemented for one of our clients is to transform these large documents into SharePoint Wiki pages and load them into Wiki libraries. SharePoint Wiki pages are widely used in organizations and easy to create,edit, share information and collaborate with others. They are very intuitive to create and use and thus easy for the users to adopt and maintain.

 

Solution diagram

 WikiMigration.jpg

 

Benefits of migrating to wiki pages:

  • Ability to edit and publish individual pages and not the whole document (that has 1000+ pages) every time a page is edited.
  • Minor versions and comments : Versions are created only for the edited pages and tracking the version is easy and color coded.
  • Table of contents & easy navigation to the pages: Relevant pages are grouped together through table of contents and quick link references to other related materials can be maintained
  • Embedding diagrams, reports, tables, lists, pictures and videos is easy. These can be simply loaded from the managed library.
  • Ability to save Page drafts and enforce approval process on publishing
  • Page rating and bookmarks
  • In-page metadata and intuitive search across pages

Summary:

Handling large electronic documents and other content can be cumbersome and time consuming for businesses, even though it is not as hard as maintaining a large volume of paper piles. SharePoint wiki pages and Enterprise Wiki sites are a simple yet effective solution that can address majority of these issues.

5 Replies
Good article! How do you perform this migration to wikipages?

Adam

I have the same question as @adam deltinger. Last time I tried to do something like this there were many limitation in the formatting of wiki pages, has that been improved?

How did I miss it :)..
I have used Word to Wiki Online app. its a nice tool .. we tried first and liked, the paid version is really good. Here is the link to the tool.
https://appsource.microsoft.com/en-us/product/office/WA104379573?tab=Overview

Ok! Thanks..I guess this will take some time for a large library  :)

Yes It is , just better than copy & pasting manually :) that was one issue what we faced.