On all our projects we first develop on our development environments, move into test, then into UAT and finally into production - so a proper DTAP deployment :)

One of the areas we always struggle with is the moving of data (e.g organisations, user groups, settings, classifications, fields) between environments. Generally we put together an Excel spreadsheet in which we update any changes when in development and run against the environments as we push through. However, this isn't the "neatest" of solutions.

Just like with the export / import of translations, it would be great if the same could be completed against other elements in the solution. That way we have an easy way of moving between environments, hopefully reducing the time it takes to achieve this and also providing better service to our clients.

ADAM has documentation on it's assemblies. I know you make a fair attempt to make that documentation as good as possible. But it will never be complete.

On some occasions you just want to see what the ADAM code is doing so you can imitate it or adapt it. That's why I prefer working with dotPeek or resharper over reading the documentation. Documentation is great for finding high level answers to high level questions. But once you're knee deep, the documentation can no longer help you.

But using dotPeek or resharper is just messy in ADAM because of obfuscation. Try figuring out how you can manipulate the OnPreCatalog so your custom indexer works exactly as the customer wants. Or try figuring out how you can create a custom FacetControl. Or try finding what ControlBuilder to override to create a custom control builder.

If ADAM dll's wouldn't be obfuscated, it would make my life as a developer a lot easier. It would make the lives of my colleagues a lot easier. They would find solutions to every day problems a lot faster, costing your/our customers a less money.

Within a PIM you are maintaining product information per product type. One application should be able to handle a product range: handle marketing products, handle food products, handle electronics, handle jewellery. For each product type/ product range you have different fields. Today you need to set the visibility based on the assigned classification. But some products are assigned to multiple classifications and then it becomes tricky in terms of displaying fields. We are at multiple customers who have a serious complex setup in terms of fieldgroups/ classifications and its not flexible enough so constantly demanding work-arounds. This is especially the case when a product hierarchy (main/sub products) is introduced.

Ideally we have the ability to set product templates which could be linked to a classification. This would allow much more flexibility, transparency and ease of use.

It would be good to have better support for Microsoft Office documents. For example, building a Media Engine based on Aspose (http://www.aspose.com/) would allow ADAM to create a preview of every slide (PPTX), page (DOCX) or worksheet (XSLX). It would also allow to extract all contents from the file.

Since 5.3 we no longer can configure spaces on the user group level, only on system level. Spaces are hidden when no assets can be found based on the users permission.

We need to be able to configure spaces on user group level as we want to present different sets of spaces to different user groups, independent of the fact that a user could find assets in a space or not. Hiding spaces when there is nothing to show would give support questions "where did my spaces go". Better would be to show the number of records in the space on the Spaces landing page.

Many of our clients request the specific custom order of panels for asset read/edit view. For example, some clients want to set the first "select classification" panel, others - upload panel. Configuration for all panels on these pages will be very useful.