Thanks @sarav_prakash  for the information provided. I think it might be this one but will await further announcement. https://developer.adobe.com/experience-cloud/experience-manager-apis/api/experimental/assets/author/

Thanks for the response - the folders are created dynamically based on the new products created and they are using a similar command as above.The aem upoad library recommended seems to have an issue so working with Adobe support on this as of now.

@sarav_prakash @kautuk_sahni Any update on this ? Please see - https://github.com/adobe/aem-upload/issues/131  

Hi all I have posted this on the github of the aem-upload library but would appreciate anyone here also can chime on this? https://github.com/adobe/aem-upload/issues/131

Javascript Use API is deprecated in AEM as A CS and Java Use API is the only recommended option for AEM as A CS. - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/release-notes/deprecated-removed-features?lang=en

I’m looking for guidance on implementing a production-ready User-Generated Content (UGC) solution in AEM as a Cloud Service (AEMaaCS).Could anyone share insights or patterns from their experience?Any advice or examples from real-world implementations would be greatly appreciated!

Thanks for getting back @arunpatidar  what we need is to create a custom schema with ALL the default tabs/fields AND additonally a custom tab with custom fields. We need to be able to do this for few different custom schemas and not just one. What we did was to copy the default schema and customised...

Thanks for sharing the screenshot @daniel-strmecki - We named our custom schema as <tenant_name>_schema and not used default as-is - I see above that you have modified or added  a custom tab within the default schema directly. Also we have multiple metadata schemas which are different to 'default'. ...

thanks for feedback @daniel-strmecki Our use case is to have the default and also our custom tabs.When I did the above I see only the custom tab but none of the inherited default tabs. We are on AEM as a cloud service. Is it possible to "inherit" default and append custom tabs in the metadata schema...

exactly - the code sample above for include is where I misunderstood (highlihted below)- our use case is to create a custom schema using the default and change them for our customer needs. The steps we took 1.Copy the default schema 2.Rename it to <customer_schema>3.Add new tabs (we have atleast 25+...