Restrict auto generation of namespace in AEM

[#1]

Description - While uploading new assets from external system, those assets might contains some metadata properties. While uploading it to AEM, it's auto generating namespace and preserving those metadata. Which we would like to prevent using this feature request if possible, Only registered namespace metadata should preserve.

Why is this feature important to you - It's creating issues while doing full text search and also impacting search speed. It certainly improve the system performance.

How would you like the feature to work - Post implementation of these restriction that only registered namespace metadata will AEM allow , when we upload any asset from any external system, it will not create unnecessary namespaces automatically into system and also no unknown properties will be part of asset metadata and full text search will work fine.

Current Behaviour - Currently if we upload assets from external system , if that assets have any metadata properties, while uploading on AEM , it's creating namespace and preserve those external metadata into the system. Also while searching system is searching assets containing those external metadata, Which causes the issues.

[#2]

@Hardik-11071994 

Please note that depending on the external tools an asset is generated/built/processed, there might be mandatory metadata that should be imported as part of migration/upload. If such metadata is stripped out from the asset it could cause an inconsistent status for the asset. So it seems there should be some level of flexibility in the destination system to comply to preserve integrity of the migrated/uploaded assets.

[#3]

Greetings @hamidk92094312 ,

Pain area :

[1] There are not any audit information on namespace.

i.e.  Who created and when? Is auto generated or manually created...etc.

So there are no ways to trace out how these external namespace coming into the picture.

[2] There is no way to find all list of assets which contains particular namespace properties. i.e. If I want to find all list of assets having namespace "ns7:" 

Issue is because of these external metadata, these assets are coming into picture while user do full text search. The assets being search not because of any metadata present with that searched keyword into internal namespace, it's coming into search because those are present in external metadata. so this is the issue.

So there should be some way in AEM to turn off binaries to import while uploading/migrating assets from external system.

[#4]

Hi @Hardik-11071994 

While we understand your specific use case, we believe the current design gives the users more flexibility and freedom while working with assets. We trust that any specific use case can be implemented as some sort of customization. Thanks for participating into this community.