51黑料不打烊

Transcript

So hi everyone. So Chindesh, are you speaking? Looks like you are on mute. Hey everyone. Hey Priyanko. So we are right now 10 people in the attendees list and we are already two minutes. So let me start the session and like we鈥檒l even like keep the chat open for the Q&A in case if you have any questions or anything, you can feel free to ping in on the chat. We鈥檒l try to answer it. So with that, let me come back to my screen.

OK. So hey everyone, this is Chindesh and along with me, Priyanko is here. We are going to talk about mastering dynamic media with OpenAPI.

Let鈥檚 talk about like before we start the session, like we are also going to have a couple of more events in this month and you can register these sessions as per you need. Like those links will be shared at the end.

Now, coming back to our topic, that is mastering dynamic media with OpenAPI.

So here is a quick agenda, what all we are going to cover today. So first of all, we will talk about the introduction, like overview of dynamic media with OpenAPI and its significance. Then we鈥檒l talk about the key differences with with respect to traditional dynamic media.

And we鈥檒l talk in terms of use cases, their best practice and notes, along with demo on a couple of major use cases. So we have like categorized a couple of use cases, which we are going to take along with our demo at the end of the session. And as I told you, like in case if you have any questions, please feel free to ping on the chat.

So with that, like before I move on to the next topic or the slide on introduction, just a quick question here. So, Priyanko, are you able to put the poll? OK. So Priyanko is doing that. Let鈥檚 talk about the introduction on dynamic media and dynamic media with OpenAPI. So I鈥檓 not sure if like how many people are aware on the dynamic media in the current list of the audience. But dynamic media is something like which is being used from quite a long time on AM, like it has been used since AM6 version, I guess, even before that. But yeah, dynamic media has been there in market for quite long. And if you talk about dynamic media, it used to deliver rich media content like images, videos, spin sets, many more on different devices and screens.

More in case in this case, we can see that dynamic media is more API UI friendly. Like you can have a proper user interface and you can interact over there. However, if I have to talk about dynamic media with OpenAPI, that is something meant for users or integrators who need automated or custom workflows. Or I can say it鈥檚 more in terms of handling the user experience of what dynamic media was providing in terms of API. So there will be not a direct UI over here, like it鈥檚 providing most of the features in terms of API so that you can use those APIs within your programs. And that is the main difference from dynamic media. And if you talk about the features, you can see the major features of dynamic media like smart imaging, video transcoding, viewer presets, integration with AM assets. And all these are like smart crops, etc. All these are like more in terms of UI friendliness.

However, in case of dynamic media with OpenAPI, those are programmatically controlled features like upload of assets, folder metadata management, image presets, publishing of workflows, all such kind of enhancements. And these are like REST and SOAP based APIs. So you can have either REST or SOAP based APIs as per your need and you can use it anywhere in terms of your need and in terms of your program requirement.

When I talk about the uses, so typically used by AM UI, which I have already talked about in case of dynamic media, asset management and publishing, like asset handling or publishing, etc. is handled inside AM for dynamic media. And if you see the URL, so URL of an image will look like this company.scene7.com. This is just a sample URL. It can vary. But the important thing is this part is image and then you can have some of the modifiers like width, format, height, etc. All those, like as per the need, you can put it over there in dynamic media.

In terms of OpenAPI, it requires API credentials and endpoint setup.

And it also like.

Yeah, and the most important part is that it鈥檚 useful in non-AM setups or complex integrations where like automatic asset processing is needed or if you need any secure asset restrictions, such kind of like if you want to make your asset restricted in some way, then in such cases, dynamic media with OpenAPI are more useful. With that, like I would like to go on the next slide.

And let鈥檚 talk more in terms of dynamic media with OpenAPI capabilities. So here we have put one short video like how dynamic media with OpenAPI capabilities can be used. As you can see, you can go in detail after like the session. You can go in detail like how all those capabilities are there. But in short, what are the major capabilities? The first one, what we have put over here is empowering user across the enterprise to access their assets across various applications without getting those many copies of the assets. So like without creating multiple copies, you can access the same asset on different devices or on different application as per your need. Then the next one is more in terms of informed decisions, like how you can make informed decisions through the assets. It will also help you to drive higher conversion and it鈥檚 30 percent faster in terms of overall performance.

And the last one is like it helps you to establish a better governance with brand approved content. So these are the four major capabilities which comes with dynamic media with OpenAPI.

OK, before we go to this slide, like I would like to have a quick poll over here.

Panko, are you able to put the poll? Yes, I already did.

OK, so here we are simply asking, can we access DM, dynamic media, OpenAPI, UI like dynamic media? So it鈥檚 a simple answer, yes or no.

All right, we are going to end this poll in three seconds.

Panko, you can end it up. Let鈥檚 see the poll feedback on the result.

All right, so we have like 12 responses and yes, like dynamic media OpenAPI, if you ask if it can be accessed like dynamic media. So basically, as I told you, like it鈥檚 mostly meant for API control, like it should be used in the programs for API and all. But if required, like you can use it via UI as well, like you can enable that feature. It鈥檚 quite simple, but it鈥檚 not straightforward like DM. It will not provide you a shared link or something like DM. But yeah, you can still access through UI. So that was a quick question. I think we just wanted to check out people know more about like dynamic media with OpenAPI. And on the same terms, we鈥檒l just go through a better list of the features or the differences between dynamic media and dynamic media with OpenAPI. If you can see the screen here, we are talking about each of the feature capabilities and what all are available with dynamic media. What all is available or not supported or supported with media with OpenAPI. So as we talk, let鈥檚 let鈥檚 go in quickly with that, like availability. We are talking like since when dynamic media is available, it鈥檚 available in premise, on premise, AMS, cloud services and all. However, dynamic media with OpenAPI is something which comes which actually came with more with the cloud service image modifiers. So we know that there are a lot of rich set of modifiers like height, width, format.

Then there are many more like I cannot name all those. But yet, but if we compare the same list of modifiers with OpenAPI, so we have limited right now. But still, like those are enough to cope up with most of the requirements. So we have highlighted here like which are mostly supported with height, width, width, quality format. We are like quite readily available and with time it will keep on increasing.

Sorry, somehow this came.

Now, let鈥檚 talk about access control. So published asset accessible to all users. There is no approval getting in case of dynamic media. However, in OpenAPI, like dynamic media with OpenAPI, you can restrict the asset by user, role, date, time and only approved assets will be delivered. It鈥檚 not like you have uploaded something. It will be available for dynamic media with OpenAPI. You have to approve it. Then only it will be uploaded. Then only it will be uploaded. In case of API tech stack, dynamic media is more so based. However, dynamic media with OpenAPI, it鈥檚 more OpenAPI based. Asset upgrade, update propagation. So here there is a major difference in CDN TTL time to lapse.

So whenever like we are making any updates or any changes on dynamic media, like the recommended CDN TTL is approximately around 10 hours. But in case of OpenAPI, dynamic media with OpenAPI, it has been reduced approximately to 10 minutes. So that鈥檚 a big, big difference over here. Approval enforcement. It updates like dynamic media will help you update auto published without approval that we have already talked. Here you require the approval reporting wise, like we don鈥檛 have a direct report for dynamic media, but there are some other ways like you can mail to a specific email ID and get the reports. But those are like very limited number. In case of dynamic media with OpenAPI, the reports based on number of assets. There is something like in progress right now. It will come very soon. Asset expiry. So when we talk about asset expiry, what happens when any asset expired in dynamic media? Like the asset will remain until unless we don鈥檛 delete it from AEM. But here in case of OpenAPI, once the assets are expired, it will be no longer available downstream. So again, that鈥檚 a major difference in both of them. Image presets, video, smart crop, etc. These are like completely supported in case of dynamic media. However, the dynamic media with OpenAPI, this is yet to like this again under process, I will say. Currently it鈥檚 not supported, but in future it may come very soon. With dynamic video encoding, there are only standard three encodes for dynamic media.

However, in case of dynamic media or with OpenAPI, it鈥檚 on on-fly encodes. Like you can have it on on-fly and there will be best formats. And lastly, the SEO part. So SEO part, like I will say that almost both are SEO friendly. There is a slight difference in both of them, but yeah, both are almost SEO friendly in this case.

With that, let me go to the next slide.

Where we talk about enabling dynamic media with OpenAPI. I will not take much time on this. Like if you are on dynamic media. So you must be having the dynamic media license. And in case if you want to upgrade on dynamic media with OpenAPI, so it will basically look for two kind of licenses, either Prime or Ultimate. So any of like if you belong to Prime or if you belong to Ultimate, you can use the dynamic media with OpenAPI. And how you can enable it. So there are simpler steps. One of these steps, as you can see that you can go to the console and you can enable the dynamic media as a feature. When you are like setting up your instances at that time, you can select whether you want dynamic media or not. So there you can enable and then you鈥檒l have to click on this button from the console to activate it. So these are the two simple steps to activate it. Maybe we鈥檒l try to capture it during the demo. But yeah, these are the only two things you have to make sure that dynamic media OpenAPI should work only if these two steps are done.

With that, let鈥檚 proceed to the next one. And once the asset is available in dynamic media, this is how it will look like.

If you see the difference on the asset right side, there are some of the properties.

Something is going wrong. There are some of the properties, whether it鈥檚 approved or not. And yeah, it鈥檚 a video. So you can play to hear the same thing. But yeah, you can see the status, whether it鈥檚 approved or not. This is the part what we were talking about that for dynamic media with OpenAPI. It must be approved so it can be used anywhere. And that鈥檚 the only thing over here. Moving towards the use cases, what all use cases we do have with dynamic media with OpenAPI.

So here I will just talk in terms of the customer challenge, which we are very frequent when we were not on dynamic media. Like one of the issue was that customer challenge or issue was that for the upload and the download process. You have multiple devices or multiple applications through which you want to upload the images or assets. So earlier, like those authors or those people who were uploading those images, they must be having the access on the AEM instances to make sure that the upload process is done properly. Somebody has to go to the AEM instances and do it. Now, this use case, if I have to say in dynamic media with OpenAPI. So since this is an API driven, you can upload or download such kind of assets or you can upload or download assets through anywhere. Since we are using the application or the API. So that that is one of the major differences here that can be resolved with the OpenAPI.

Moving towards next one, lazy loading and poor performance of media on channels, which was like causing all the like speed issues or something. Quality and speed issues. So for that, again, like as we have already talked about that dynamic media with OpenAPI is quite faster. It鈥檚 almost 30 percent faster from the previous one. And also like how it is faster, like it improved the core web vitals by enhancing your image delivery performance based on the different browser capabilities and the which exact browser are you using. Based on that, it will keep on changing the image vitals as per the need. And that鈥檚 why I like it鈥檚 quite faster when we talk in terms of OpenAPI.

Heard issue like this is something risk of compliance without governance and security. So let鈥檚 say I鈥檓 an old AEM customer and like I鈥檓 on the old AEM and some customer. I am not following any specific governance or any governance for the compliance or security. Maybe I have not enlisted any security kind of thing. Then there is a high risk of losing my data or losing the information related with that data. Now, that part can be easily resolved from OpenAPI since it will help you to only allow such kind of assets which are approved. There is a channel now which will help you to make sure that what all assets you want to share. And based on the APIs, again, you can control what all data you want to share so that there is some channel. There is some feature provision which have filled that gap. I will say talking in terms of the last one, lack of understanding where content is delivered. So this is again better in terms of OpenAPI since it gather metrics for like where your assets are going to be delivered to understand the uses of downstream work. So basically, as per your device, like where exactly it has to be delivered, it will provide you a better metrics. And in that case, OpenAPI is a better one.

I know we are already on time. So these screens are like more like it鈥檚 talking about what all other features are there. So if you see the deal with OpenAPI can be easily integrated with 51黑料不打烊 applications like Target or any campaign, etc. However, if we talk about some third party, maybe Salesforce or Google Workspace or Drupal. So those things are also something like supported dynamic media with OpenAPI and many more integration with third party is possible. So all those information are supported, provided in this deck itself. You can browse it and let us know. Last but not the least, how you can enable the AM side. These are some screenshots like how you can make sure that dynamic media with OpenAPI works with AM sides, how it works with non-51黑料不打烊 applications. And we have provided some videos. So without wasting much time, I鈥檒l just ask Priyank who to go for the demo.

Thank you, Chandesh. So I鈥檓 going to share my screen for the demo.

OK, so as Chandesh has talked about, you know, you can enable this dynamic media with OpenAPI on your assets environment.

And so this has to, since this is supported only on cloud. So once this gets enabled on your assets environment, there are things that you need to be aware of because generally the enterprise assets environment do not have publish setups.

And to manage the workflows for delivering these assets follow a different route, which is more or less based on the metadata of the assets. So if I have to show you, you know, how which metadata is important for the delivery of these assets to make sure that these assets are available to the applications where you want to consume it. You need to, you know, go to the metadata.

So this is the assets environment where we have enabled dynamic media with OpenAPI. Now, if I open this and, you know, open the metadata of this asset, I can see that there are some, you know, metadata properties. So these two properties are of important use. One is the review status. So if the asset is approved, so that means that this asset is a brand approved asset and is available for the consumption to your third party or maybe your AM specific application. It has multiple options to support your use cases. But, you know, the asset will only be available to the delivery tier. So with this, once you enable dynamic media with OpenAPI, it gives you a delivery tier from where your assets are going to be served. So those assets will only be available on the delivery tier if those assets are approved.

Second important property is of rules. And we are going to see a demo of this, you know, how this rules works. So essentially, Chandesh talked about the restricted asset delivery use case. So with this option, you can add as many rules here and you need to configure some of the things which when we come back to the demo of the restricted delivery, we鈥檒l talk about. But this is an important property to support the use case of restricted delivery. Now, once the asset is approved, so this is how it is going to appear on your touch UI based, you know, view. So here you will see a check icon which tells you that this asset is a brand approved asset and is available on the delivery tier. Similarly, if you are using new asset UI, you will be able to see this approved option available here, using which you can, you know, identify which assets are approved and which assets are not.

Okay, now, so this is how the UI after dynamic media with asset environment with dynamic media with open API looks like and how you can utilize the workflows of, you know, making your asset available to the delivery tier. Then let鈥檚 talk about integration scenario. So here I鈥檓 talking, I鈥檓 taking a use case where, you know, your assets are residing on your enterprise asset. And then you have a site instance from which, you know, is going to pick the asset using the dynamic media with open API. Now, before dynamic media with open API, we used to have something called connected assets for that use cases. But in those scenarios, what used to happen that it duplicates the assets, but with dynamic media with open API, you know, those assets are not duplicated and, you know, your enterprise asset can serve as a single source of truth. Now to showcase that use case, let me go to the site instance. So this is the site instance where we have, you know, set up the weekend site and this is one of the page. So let me just refresh this page again.

So, you know, dynamic image with three core components support dynamic media with open API. So I鈥檓 using that to show that integration. So if I click here and open this image component, I鈥檒l see this option here. Local means you can pick asset from your local site instance.

And remote means that you need to pick your asset from your remote time instance. So there are some configurations that needs to be done at your AM site to make this integration work.

And once those, you know, configurations are done, you will be able to see this option appearing here. Now for this use case, I need to select an asset from my remote time instance. So I鈥檒l click on the remote option. It is going to ask for authentication for your credential for the authentication. So now I鈥檓 logged in to my assets instance with my ID. I am able to see these assets. So you can see all the approved assets appearing here.

And now let me select one asset for this use case. Let me select this.

And let me put some alt text.

And let me just save this component.

Now if you look at this, the URL of, so let me go to preview. And if I have to show you the URL that is being generated, it is not from, you know, your site instance. It is taking the asset from the delivery tier. And we will see, you know, how this delivery tier URL works. But essentially it is picking the asset from the delivery tier of your enterprise time instance rather than picking it from your own site instance. So this is the same as the remote time instance. And this, again, your asset is not getting duplicated. You are utilizing the same asset that is uploaded on your remote time instance.

Okay. So, yeah. So now we, so this is on AEM side of it. If you have a use case where you want to, you know, let鈥檚 say you have a different CMS and then you have your enterprise dam assets with dynamic media open API enabled on AEM. And you want to use, utilize those assets on your third party, you know, application or maybe third party CMSs. You can build those integrations. So 51黑料不打烊 does provide some micro front end, you know, application which can be customized to your need. And that can also serve the purpose of bringing the asset from the remote dam instance.

Now, let鈥檚 talk about the APIs as well.

As Chandesh already highlighted, we, so this capability also is open API based. So it provides several, you know, APIs using which you can interact with your remote dam instance to bring in the asset and to build the integrations as per your requirement.

Now, if I, so this is one of the API which is specified for, which is for searching the asset. Now in this, you need to provide some queries so you can provide a detailed query in the JSON format. So this is the format that we are using. So we are matching for restricted, read and sample. So whatever assets we have, if they have a matching text with starting with restricted, read, or anywhere in as a sample, so that should appear in the response. Then it requires a bearer token which can be generated from your IMS API or you can, I mean, for the development purposes, you can use the local token as well. But in those, in the production scenarios, it is, you know, you should use the IMS based token generation mechanism. Now, once the bearer token is provided and, you know, you need to set some headers, your XAPI keys, which is provided by Ruby. So once this is enabled and when you click hit, it is going to search for the assets.

So you can see the results are coming and so this have read in it, restricted in it, and then, you know, sample in it. So this is how it is going to search the asset. Next is the delivery of the asset. So if I show you, you can, you know, request any rendition of that asset. You can, you know, ask dynamic media with open API since it is using a delivery tier, which is powered by Fastly. It optimizes the delivery of assets and you can rely on dynamic media with open API to, you know, to deliver the most optimized version of the asset as well. So here I am just showcasing one of the scenario where you have requested for the rendition and it has returned the rendition for that as well.

Now for the scenario, so this is one of the, so this is the original asset. So if you look at the URL, so it is a delivery tier URL. You can obviously customize it according to your need as well. But by default, this is what, how the delivery tier looks like. So this is the delivery domain URL and then you need to provide the assets UUID. And then this is the rendition name and then you can provide the SEO name and then this can be done programmatically. You can pick your metadata values and put it there and it is going to and then this is done for the SEO purposes. So once you make a request, it is going to bring in the original asset rendition. So you can see the size of this asset is 578.3KB because this is an original asset. Now, if I don鈥檛 provide any, if I have not, if I鈥檓 not requesting any original asset or any, you know, any rendition of that asset, I just provide the asset ID. I am going to, you know, the dynamic media with open API is going to deliver an asset which is optimized. So earlier the size was somewhere around 500KB. Now it has reduced to 131KB. So a reduction of almost five times. So it is done automatically. So as I said, you can always, you know, request the specific rendition for your use case and you can also apply some of the, you know, operations as well. So here if you look at, so you can provide the format and here if you look at, I have provided a modifier to rotate this asset. So it has rotated this asset to my requirement.

So there are certain limited set of modifiers that can be used, but they work absolutely fine with dynamic media with open API.

Now you can always request, you know, metadata of the asset using the asset UID and which, you know, in case you need it. So this is about the APIs.

Now the next use case I鈥檓 going to talk about is the restricted delivery. Now during the starting of the demo, we talked about one of the metadata field rules, which is a multi-field and you can, you know, configure as many rules as you want. But, you know, if you look at the format, I mean, here I am using IMS to restrict the delivery of asset. You can also have, you know, your own SSO-based triggering of that. So here if you look at the format, there is a separate way of, you know, doing that, but with IMS, it is supported out of the box. Now here if you look at, so this is the org ID. So anybody who is familiar with admin console, so there is org ID, which is specific for your organization. And then you can have your user IDs or maybe the groups that you create. So these restrictions can be done at group level, can also be done at individual level as well. So this ID can be for the group or can be for the individual and you can add as many, you know, roles as you want here.

And once you do this and once you publish the, or, you know, activate or approve this asset, it is only going to be visible to the people who are part of, maybe depending on the group or the user you have configured here. Now, if I have to show you one use case, so let me open admin console. Just give me a second, please.

So yes, so this is the admin console group that I have created and you can see that I am part of this group, whereas Chandesh is not part of this group. And the org ID and the group ID that I was talking about, you can find this in the URL as well. So this becomes the org ID and after the user groups, this becomes the user ID. And this is how it has been configured here as well. So first org ID and then we have a column and then we have the user group ID. Now, since I am part of this restricted group and when I requested, when I searched the assets using this, I was able to see the restricted asset because I am part of the restricted group. Since Chandesh is not part of a restricted group, I am going to use a token generated by him for the purpose of this demo. So I鈥檒l use the token he generated and I鈥檓 going to remove the token that I generated. And when I request this, okay, so Chandesh, so yeah, so as of now, this token has become invalid.

So once he gives you another or once you generate a different token, then he will not be able to see that here. So Chandesh, if you鈥檒l be able to generate a token right now, we can.

Yeah, give me a minute, I鈥檒l try to do that.

Okay, so in the meantime, we do have some questions as well, I think.

Okay, thank you. Can you try? Yeah, just give me a second, please.

Yeah, so he don鈥檛 see that asset, only two assets are being displayed for him because he鈥檚 not part of that group.

So now there is some best practices that needs to be followed.

So for dynamic media with open API, so there are some things that you need to be aware of when using dynamic media with open API.

So dynamic media with open API, I mean, if you鈥檙e using it on your site鈥檚 instance, then it must be on service pack 18 or later. And if you鈥檙e utilizing the core components for using that, you need to be on core component version greater than 2.23.2. And, you know, dynamic media open API only works on AM asset as a cloud.

The best practices are that for this to enable this, you will require to provide some, you know, values, some credentials. So as you have seen that, right, so it is recommended not to hard code the credentials, use environment variables to do that. And then, yeah, and just let me go back to we have talked about core components, best practices and nodes. And then at the end of the slide, I have added some of the references which you can look at. And that brings us to the end of session today. Thank you.

So thank you, Priyanko.

And we have just posted one link for the survey of the overall sessions. So please let us know your feedback. And in case if there are any more queries or any more feedback, let us know. So with that.

Just look for any more questions, so we don鈥檛 have any more questions. Yeah, so thank you, everyone. Thank you for giving us time to talk about this dynamic media with open API. And yeah, feel free to reach us or reach to us in case if you have any further queries on dynamic media with open API. So thank you all. We鈥檒l end up this session now. Thanks.