Webinar Announcement: How to better manage your metadata so your teams receive content faster!

August 12th, 2020

You can have the best Digital Asset Management system known to DAM, but if your metadata is weak or entry is lagging, 

a return on investment bottleneck begins to grow and your assets do not reach the teams that need them.

How is that affecting your business today?

Join experts from My DAM Services as they provide insight on how to accelerate time to market and further improve your digital asset management return on investment!

In this webcast, you’ll hear:

·         How to remove bottlenecks

·         Gain more efficiency from your DAM Managers

·         Ensure continuity in operations

Zoom Link info below - https://bit.ly/3k1IjhU 

Sitecore Content Hub Guild Webinar:

How to better manage your metadata so your teams receive content faster!

Wednesday, August 12, 2020

9:00 AM Pacific Time/ 12:00 PM Eastern Time

 

The Copernicus Moment and Sitecore Content Hub

For those who don't know who Copernicus, he is the one whom came up with the controversial manuscript stating that the planets revolved around the sun and not the earth. People had these very complex diagrams on this worked but once people believed the true science then everything became simpler.  This controversy was more intense then the SiteCore vs Sitecore debate.

Now let's look at Sitecore.  Consensus in the community is Sitecore is the center of the content manager's solar system however with the introduction of Sitecore Content Hub this changes. Content Hub is now the center of the solar system.  What? But content editors live in Sitecore.  Well not exactly. Just like the scientists in Copernicus' time they worked in other systems but pretended for the techies creating the solutions that Sitecore was the center.  Marketers worked in Adobe InDesign, Hootsuite, WordPress, blogs, and a myriad of other tools.

By placing Sitecore Content Hub in the center that means the marketing manager can create the project for their campaign, they can create tasks for all parts of the campaign which may include:

• Creation of assets
• Creation of all content (blogs, sitecore content, online and physical ads, flyers and posters, etc)
• Obtaining rights to content and/or assets.
• Edit assets and content.
• Approve assets and content.
• Publish the assets and content
• Keep track of the project and determine how a delay will affect the campaign delivery.

Now as a content editor you can still go to InDesign or Sitecore or other applications and use the content. You can still use your placeholders and personalize like you did before.  You don't lose any of that.  What you gain is efficiency.  Rather than switching systems to create, approve and publish content and/or assets you go to one system and see the whole picture. As an added bonus, having all the assets in one spot there is less chance that someone is using the wrong version or is unaware of the new version.  Rather than searching through emails and file shares for the latest version of an asset you can go right Content Hub and search for it.  

This is a Copernicus Moment for the Sitecore Community. Some will rebel I am sure but in general this is a big plus for marketers that need all the time they can get for marketing campaigns as they are way behind and working evening and weekends to get it done.  

If you have any questions feel free to reach out to me. I will be at Sitecore Symposium. I arrive on Sunday and don't leave until Saturday. I am happy to chat in person about this. If you have trouble finding me drop by the EPAM Systems booth and ask for Chris Williams.

Choose Unique And Multi-value Wisely When Adding Option List as property to a Schema

When building all the schema you will determine the properties as best you can but will want to add or change schema later.  In some cases that is cool but in other cases changing the schema can be a challenge.  One such time is when working with option list properties. In the screenshot below I have highlighted 2 properties: Unique and Multi-value. Once you set these values and save them you cannot edit them.

This is new member

Note that after save we go to edit and see this. Note you cannot edit.  This is by design because as a developer you know the implications of changing these once you have data in these fields.

So be careful when choosing the options. Now there is a way to fix it afterwards but not a nice one  The way to fix it is to create a new property with the proper settings then use script to migrate the data to the new property, flagging any with possible issues for manual fixing later. 

If you have more of these please let us know and we can add them.

Integrating with Sitecore Content Hub

There are 2 sets of APIs you can use to integrate with Sitecore Content Hub:

1. REST API: These APIs allow you to use Standard GET, POST, PUT and they return JSON. Well that is the high level description of them. You can find more in the REST API documentation. We have also created a simple .NET Core Console application called SchBasicCoreConsole which provides a sample of some of the API calls to get you started. You can find the source code as well as the binary in the SchGuild Git repository.   
2. WebClient SDK: To use the WebClient SDK you require the Nuget packages for it. These are available via MyGet. This article explains how to get the packages. You can find out more in the WebClient SDK documentation. We have created a simple .NET Core Console application which will be available soon. It provides a sample of calling the WebClient SDK to perform some tasks. 

Out of the 2 options we highly recommend using the WebClient SDK for a couple reasons. The first being that WebClient SDK handles a lot of the package formatting which can be error prone. The second being that the Script SDK which is used within Sitecore Content Hub itself uses the same object model so most of the code you do for WebClient SDK can be repurposed for Script SDK.

Any MVP will tell you that the best way to figure out how something works is to decompile the DLL and take a look. In the era of Web-based solution, Fiddler is the equivalent . If the API is not mentioned in the documentation or you need access to the actual JSON response rather than the object model, then the WebClient SDK has the Raw method. This method will pass the proper token for you and allow you to do a raw GET, POST, PUT, DELETE asynchronously. It will not pass in all the headers for you but it is quite useful. You can read more in the IRawClient documetation. For an example of how to use it for POST download the SchWebClientCoreConsole from GitHub and look at the GetAllScriptsAsJson method of the WebClientContext class.

If you have any questions about Sitecore Content Hub feel free to email me. Also if you have access to Sitecore Content Hub and want to help us extend these examples or work on some other open source initiatives we have planned then reach out and we can collaborate so everyone can benefit from this on their first integration. You can email me at christopher_williams@epam.com

If you are going to Sitecore Symposium then you will see Jose Dominguez, Brent Pinkstaff and I wearing a "You Had Me At Metadata" t-shirt. Stop us and say hi.

Techie's Description of Sitecore Content Hub

I have had a few people ask me about Sitecore Content Hub and as a techies some of us are not as familiar to marketing.  So I decided to describe it in terms developers understand.  Let's look at source files in your website build.

Consider the assets that marketing talks about to be your source files, your Javascript libraries, your CSS files.  Now that needs to be store somewhere and be versioned. Depending on your product you may need to support multiple source languages especially if you are developing an API. You may have a demo for python, java, C#, etc.  A change in the API for the new version and you need to update all those demos.  This is where a DAM comes in. The DAM is like Git or Visual Source Safe :)

Now you have to build your solution and deploy it, that is where Content Marketing Platform (CMP) comes in. You manage your content and push it to wherever it needs to go.  Sitecore, a feed, social media posts, etc. This is the equivalent to Azure DevOps which provides you a build pipeline and release pipelines to get it in to the various environments.

Okay but is there anything to do project scheduling, raise issues, track tasks, etc.  Well there is and it is called MRM.  Marketing Resource Management and that is pretty much what it does.

This is kind of high level so if you want to dig deeper let me know and I can answer questions but hopefully that gives you a better idea on what each part is in terms of techie terminology.

What is Sitecore Content Hub?

With the release of Sitecore 9.2 came the announcement of Sitecore Content Hub 3.2. Now initially people saw it as Sitecore DAM but that is incorrect. Sitecore Content Hub is actually a variety of components, some you can use stand-alone while others are built on top of other components.
Let's take a look at the various components:

• Sitecore DAM: This is the Digital Asset Management part. You can import or upload your assets, assigned their metadata, edit the metadata and set up permissions and workflows. All the stuff you would expect of a DAM.
• Sitecore CMP: This is your Content Marketing Platform. Now the way I understand it is you use this to manage all your marketing like social media posts, etc. I am new to this so I will write up something bigger later or update this later with more as I learn it.
• Sitecore MRM: This is your Marketing Resource Manager. So as a developer you can think of it this way. Jira is to developers as MRM is to marketers. Now that is oversimplifying it but it gives you a good idea on what we are referring to.
• Sitecore W2P: This is your web-to-print. So for those familiar with Sitecore you probably know about PXM. This is kind of like that. You share your content from web CMS inside your print layouts for flyers, posters, PDF files, etc. with the same personalization and such you get on the website
• Sitecore PCM: This is kind of like your DAM but specific to your products, relating all the assets for that product together.

If you have more questions please reach out to me at chris.williams@readwatchcreate.com

Introduction To Sitecore Content Hub Guild

Welcome to Sitecore Content Hub Mentoring Guild. Through this site we will share information on what Sitecore Content Hub is and dig deep into how to configure and extend it. We look forward to learning together.

If you are non-technical or less technical then please check out or DAM Guild which is more marketing focused and shares more general information on marketing concepts.

You can access Sitecore Content Hub Mentoring Guild on various channels:

• Twitter: @schguild 
• LinkedIn: Sitecore Content Hub Mentoring Guild 
• Blog: schguild.blogspot.com - you are already here.
• GitHub: https://github.com/sitecoreguild/schguild - currently all on develop branch.

To start with take a look at this article to get an idea what content hub is.