Gold Sponsors Bronze SponsorsSilver Sponsors Document Conversions, why we need it and what are the options? Colin Gardner Kaboodle Software

In this session

Foundations An Anatomy of Information Products Information Product Media The Document Lifecycle

An Anatomy of Information Products

A few examples DocumentScopeLongevityValue OrganisationalTransientTrivial Team/Dept.TransientImportant Team/Dept.Semi-PermanentImportant OrganisationalPermanentStrategic OrganisationalSemi-PermanentStrategic Organisational & External/Public PermanentStrategic External/PublicPermanentImportant

Information Product Delivery Mediums types-of-information-products-are-there/ Try to think of a document as information that is delivered in a container Information producers have different needs to information consumers Different containers are better suited for different purposes So why would we use the same container for both producers and consumers?

Document Lifecycle If it is accepted that needs of information producers and consumers are different (and archivists have their own needs as well) we have a business case for format conversion

Candidates for Conversion Above, Below and Beyond the Line Format options, Word, pdf, xps, ePub, wikis The good, the bad and ugly about wikis What about the IM Nirvana of Currency and Consistency? Think renditions and not copies

Above, Below & Beyond the Line Productio n Utilit y Retention/Dispo sal

Format Options

Wikis: The Good the Bad and the Ugly (Wikis in general and SharePoint Wikis Specifically)

Wiki Woes for Content Authors

The Nirvana state of Information Management is a single source of truth for then we have: Currency: Everyone is working to most up to date information Consistency: Everyone is working with the same information But surely if we create different copies of documents (as we have to if we want them in different formats) then we risk compromising currency and consistency IM Nirvana: Currency and Consistency

Think renditions not copies

Technology Options Microsoft Client: MS Office Microsoft Server: Open XML SDK, Word Services (demo) 3 rd Party Extensions (Muhimbi, Adlib (demo), Aspose, Kaboodle Converter (demo) ) Kaboodle Word to Wiki (demo)

The HR department is updating the policy document which covers good conduct standards expected in the work place The document is to be revised initially by the HR department internally and when approved it needs to be published as a pdf in the company policy library which accessible to all employees. Use Case Scenario 1

Microsoft Client: MS Office

Microsoft Server: Open XML SDK and Word Service

Word Service Demo

3 rd Party Offerings

Muhimbi

Adlib

Adlib Demo

Aspose

Kaboodle

Kaboodle Renditions Converter Demo

The widget development department of Widgets R US maintains publically accessible information on the web pages of the company’s public facing web site in O365/SPO and needs to update regularly update product descriptions Use Case Scenario 2

Renditions Word to Wiki

Renditions – in Summary

Wrap-up

A few lessons learnt

Question and Answer

Blog Posts The case: Wiki Woes: Overview: Part 1: Part 2: Part 3: This Presentation Link from Demo Solution (.wsp) Source Code (.zip) References: Blog Posts and Downloads

Word on the server – don’t do it What’s new in Word Automation Services Open XML SDK Scot Hillier - REST Service 1e0578a1#content References

Muhimbi ADLIB pdf.aspx Aspose Kaboodle Renditions References: 3 rd Party Products

Come see me at SPC14 Santos Case Study Integration of SharePoint with Oracle Spatial

Gold Sponsors Bronze SponsorsSilver Sponsors Thanks for listening Remember to submit your feedback so you go in the draw to win prizes at the end of the day

Add finally, finally 1.When I was little 2.Simple 3.Gone 4.Every word 5.Hours 6.Ceasefire 7.Faded colours 8.Before I called you mine Produced by John Hilliard Caitlin Gardner When I was Little