Friday, November 22, 2019

Changing the Image Export Size from PowerPoint for Office 365

I am working on a new YouTube channel called InfoSciShow™. I'm really excited about making these videos and have several in the works for launch this month. Please subscribe to my channel!!! I promise you won't be disappointed.

So as I'm building my visuals in PowerPoint, I did a test export of my custom thumbnail slide. There were no options for changing the size of the exported image. The resulting image is 1280x720 for both PNG and JPG exports. Not exactly 4K! Note: I was using the standard 16x9 slide size of 13.333" x 7.5".



No, the "More options..." doesn't give you this option, though it does let you add metadata.

So how do you change the resolution of slides exported as images from PowerPoint? I'm using the latest release of PowerPoint for Office 365 on Windows 10.

Turns out you have to edit the Registry. WHAT?!? It's 2019, right? With all the great features in PowerPoint, why is there no option in the app for changing this value? You can even export presentations as a 4K video, but not a slide. 🤔

While I'm on this topic, the Microsoft Doc called "How to change the export resolution of a PowerPoint slide" uses the term DPI when it means PPI. Yes, I know this is nitpicking and they effectively mean the same thing. But DPI (Dots Per Inch) is a physical print term. PPI (Pixels Per Inch) is the proper term for anything digital, including scanner settings from physical to digital. (This will probably be covered very briefly in one of my videos...)

So, I'm off to hack my registry.

If you know a better way, please leave me a comment!

UPDATE

If you want to set PowerPoint 2019/Office 365 to export slides as images at 4K (3840 x 2160), do the following—at your own risk!

You will need a PPI (DPI) number for the registry edit. What number?
  • If your slide size is the standard 13.333" x 7.5" (16x9), PPI needs to equal 288.
  • If your slide size is custom, e.g., if use are using a custom template, and is 26.667" x 15" (16x9), PPI needs to equal 144.

Go to this part of the registry:
Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\PowerPoint\Options
Once there,
  • Add a DWORD value.
  • Name it "ExportBitmapResolution".
  • Change it to decimal.
  • Set the numeric value.

Yes, that's a setting of 288 "DPI" for the standard slide size for 16x9 aspect ratio. I figured out the math based on the examples in the above linked article. The registry will convert this to a hexadecimal value of 120 (FYI).

You should close PowerPoint before this and relaunch it after the change. BE CAREFUL in your registry, and don't come to me if you mess it up.

Monday, September 9, 2019

Speaking at ARMA InfoCon 2019 in Nashville

I'm excited to be speaking at ARMA InfoCon 2019 in Nashville this October. This will be my first time speaking at an ARMA conference, though I know many of the other participants and speakers quite well already. I really appreciate ARMA for this opportunity.

One of my sessions will be an extended presentation and conversation on Information Analytics. What is it? What are the types and other names and tools that include information analytics? What is it used for? How can information professionals leverage these tools to support their organizations?

See you there?

Speaking on Office 365 at ARMA NOVA in September

It's been forever since I posted here on my personal blog, but I'm still kicking and still engaged.

This month I will be speaking at ARMA NOVA's first program of the year on Office 365 on Sept. 18. Register on their website.

In October, I will be speaking at ARMA InfoCon 2019 in Nashville. Check it out!

Friday, September 21, 2018

AIIM Webinar: Effectively Capturing Paper and Digital Documents in your Existing Applications

On September 19, 2018, I was the featured speaker for this AIIM Webinar on intelligently capturing documents into existing LOB applications. The slideshare also includes the YouTube replay. Or you can just watch the replay from this post below.

SlideShare Deck:


YouTube Replay:



In this webinar, we share best practices for the capturing of key information and data from paper and electronic documents and forms. We discuss:
  • The value of must-have features including OCR, image and file compression, redaction, and group collaboration – without altering the original file
  • Why all companies in any industry and of any size need to take advantage of these modernization efforts
  • How simple solutions are readily available, with easy integration into your existing applications.

Thanks to AIIM, the Association of Intelligent Information Management, for the opportunity to present at this webinar.

Saturday, June 9, 2018

Information Governance Conference 2018 Keynote Announced

The Information Governance Conference, or InfoGovCon, is a fantastic event for information professionals run by my friends at the Information Coalition. This year's event, held September 25-28 in Providence, will mark InfoGovCon's 5th year. I spoke the last 2 years, and I won the 2016 Information Governance Expert of the Year award.

At #InfoGov18, I am excited to be a keynote speaker, kicking off the very first Leadership Development Summit. And InfoGovCon is a prestigious event. Last year, one of the keynotes was the Governor of Rhode Island, who gave a very informative talk about delivering information technology solutions to public sector customers. That's the kind of company I'm in!

This was the announcement yesterday from InfoGovCon:


Get your tickets for #InfoGov18 today!

Saturday, March 17, 2018

User Object Attributes in Office 365 Exchange Online

I was working with my team on using our Exchange Online user attributes to create a new custom signature. But I could not find a definitive reference listing the user object attributes. So I went back to PowerShell and got it myself.

I did this by getting a user object and exporting it to a CSV file. These are all the attributes I found with "Get-User".

There are also custom attributes available as part of an ADUser object. I still have some digging to do. These are mapped as extensionAttribute1, extensionAttribute2, and so on. I am not certain how all these map to each other, so your mileage may vary.

Note: Some of these are more important that others, and some are likely deprecated or obsolete. Use this list at your own risk!

Attributes

AccountDisabled
AdministrativeUnits
AllowUMCallsFromNonUsers
ArchiveRelease
AssistantName
AuthenticationPolicy
CertificateSubject
City
Company
ConsumerNetID
CountryOrRegion
Department
DirectReports
DisplayName
DistinguishedName
ExchangeVersion
ExternalDirectoryObjectId
Fax
FirstName
GeoCoordinates
Guid
HomePhone
Id
Identity
Initials
InPlaceHoldsRaw
IsDirSynced
IsLinked
IsSecurityPrincipal
IsShadowMailboxProvisioningComplete
IsSoftDeletedByDisable
IsSoftDeletedByRemove
IsValid
LastName
LegacyExchangeDN
LinkedMasterAccount
MailboxLocations
MailboxProvisioningConstraint
MailboxProvisioningPreferences
MailboxRegion
MailboxRegionLastUpdateTime
MailboxRelease
Manager
MicrosoftOnlineServicesID
MobilePhone
Name
NetID
Notes
ObjectCategory
ObjectClass
ObjectState
Office
OrganizationalUnit
OrganizationId
OriginatingServer
OtherFax
OtherHomePhone
OtherTelephone
Pager
Phone
PhoneticDisplayName
PostalCode
PostOfficeBox
PreviousRecipientTypeDetails
PSComputerName
PSShowComputerName
RecipientType
RecipientTypeDetails
RemotePowerShellEnabled
ResetPasswordOnNextLogon
RunspaceId
SamAccountName
SeniorityIndex
Sid
SidHistory
SimpleDisplayName
SKUAssigned
StateOrProvince
StreetAddress
StsRefreshTokensValidFrom
TelephoneAssistant
Title
UMCallingLineIds
UMDialPlan
UMDtmfMap
UpgradeDetails
UpgradeMessage
UpgradeRequest
UpgradeStage
UpgradeStageTimeStamp
UpgradeStatus
UserAccountControl
UserPrincipalName
VoiceMailSettings
WebPage
WhenChanged
WhenChangedUTC
WhenCreated
WhenCreatedUTC
WhenSoftDeleted
WindowsEmailAddress
WindowsLiveID

Friday, December 15, 2017

CMSWire Article: Why Customer Experience Needs Information Governance

My latest CMSWire article is "Why Customer Experience Needs Information Governance":
Customer experience management is generally the domain of the chief marketing officer (CMO) and the marketing department. Information governance usually falls into the domain of attorneys and records managers. It’s time these two groups got together to explore ways they can serve their organization’s mission better as a team.

Read more »

Sunday, July 9, 2017

Content Cleanup and Migration Planning

When planning a new content management system, you almost always have to plan for content migration. It doesn't matter if you are working with enterprise content, records, knowledge, data, or even web content.

Migration means moving content from a source to a destination. Often it is from multiple sources to at least one destination. Here are some important considerations:
  • If there are any information architecture changes required, the migration will be more complex than a simple "lift and shift" of content.
  • This is often a great time to clean up information ROT (redundant, obsolete, trivial). This can make the new information repository cleaner and often lower the effort of the actual migration process.
  • The process has to be planned and executed carefully and with adequate change management to avoid problems:
    • The migration should usually be done at a time when no users are interacting with the content, otherwise you will have to deal with the delta of change in the content.
    • The process should be planned and tested in a staging/testing environment in order to verify that all the content will be moved correctly by the planned migration process. If there are issues, revise and repeat until it works and has been verified. Then throw that test data away and redo the migration to the new production destination, allowing for much higher likelihood of success and avoiding a delta of content to reconcile.
    • People who interact with the content as part of their job need to be informed and then verify that they have the information in the new location and can do their jobs. A little training at this point will go a long way toward successful adoption of the new solution. Remember: You are not just migrating content, but also people and processes.

Another thing to keep in mind is this: Depending on the information architecture, which should largely depend on your business processes, not all content necessarily has to be migrated at once. Focus on units of content that would cover individual business processes if it would work better to migrate in phases.

For each phase of migration, the following process can be adapted to your needs to ensure a successful content migration.

Stage 1: Plan

  • Determine migration requirements.
  • Inventory source content and metadata.
  • Determine records and information management requirements.
  • Create destination site architecture and design.
  • Create cleanup and migration plan.
  • Develop test plan.
  • Communicate migration plan to affected users.

Stage 2: Test

  • Create staging site for test and cleanup.
  • Migrate a copy of the source content to staging site.
  • Test content cleanup in staging site.
  • Validate test cleanup and migration.
  • Customize cleanup and migration procedures.
  • Dispose of test content.

Stage 3: Migrate

  • Make sources read-only.
  • Migrate content to staging site again, for final cleanup prior to migration to final destination.
  • Perform content cleanup.
  • Create the production site for migration.
  • Migrate cleansed content to target site.

Stage 4: Validate

  • Verify successful migration completion. If anything goes wrong, you can back out by unlocking the source repositories for continued use while starting this planning again for a future attempt.
  • Create migration report.
  • Conduct migration completion meeting.
  • Dispose of staging content.
  • Decommission source content and source repositories according to retention policies and requirements.

I plan to write more about each of these steps in future posts.

A note about grammar here:
  • "Clean up" is a verb phrase, as in "You need to clean up your content."
  • "Cleanup" is a noun, as in "This is the plan for content cleanup."