Thanks for attending my session at SharePoint Saturday New England, sponsored in part by BlueMetal!
Pre-Session Playlist
- Strange Desire – Rollercoaster
-
Thanks for attending my presentation at this month’s Granite State SharePoint User Group meeting!
-
With SharePoint Feature Pack 1 (November 2016 Public Update), Microsoft has addressed a key shortcoming in maintaining enterprise managed metadata across SharePoint Online in Office 365 and an on-premises environment. In preview, this feature allows one to now be able to implement a taxonomy across SharePoint Server 2016 (or SharePoint Server 2013) and SharePoint Online. Enterprise content managers… rejoice!
With the availability of this capability, an administrator can now either:
- create new term sets in SharePoint Online and/or
- copy existing term sets from SharePoint Server to SharePoint Online with Windows PowerShell,
then have them replicated daily in a read-only state back to SharePoint Server. This means that you can create your ‘master taxonomy’ from your existing taxonomies while maintaining the GUIDs of the terms, term sets, and term groups.
While this is a huge step in being able to maintain a comprehensive enterprise information architecture in a hybrid SharePoint configuration, what is still lacking here is a master Content Type Hub where content types could be published in SharePoint Online and be subscribed to both from there and from SharePoint Server. This would complete the paradigm for managing content types and site columns that potentially map to those term sets that would now available universally with this new unified taxonomy.
Read more about how to set up this capability here.
Related Links
-
Microsoft has released guidance on how tenant and site administrators can enable and disable the new SharePoint document library experience for users. See this article:
Using this method, I was successfully able to alter the user’s experience, but here is a caveat… When you alter the setting in the SharePoint Admin Center:
the effect is not immediately apparent. There is a delay between when you make the change (to either choice) before a user will notice. SharePoint Online must be going through programmatically and changing settings at a library level. For my test, I only have one site with one document library in it in the entire tenant, and it took between 30 and 60 minutes to update.
Also I noticed that Microsoft is calling this setting SharePoint Lists and Libraries Experience, even though the settings provided are only exposed for libraries, not lists. Is more change to come to our list views?
Related Posts
- New SharePoint Document Library Experience (04/19/2016)
Categories
Adoption Agile AI Bugs Cloud Delivery Excellence Digital Strategy Enterprise Content Management Humans Hybrid InfoPath Information Architecture Information Governance Information Management Knowledge Management Meetings Navigation Office 365 PowerShell Presentations Resources Sample Data Sets Search SharePoint SPS Events Tools User Experience Web Content Management Workflow
Content Precedes Design 