Users of Brand Portal

Hi Fabi, 

i am interested to join this chat.
We are currently implementing BP and my experiences are not that old and i do not have a lot of time with the system yet.
I have currently a few struggles to get this up and running.
So i might tell you a bit about the challenges we currently have and some good news how we fixed a few of the challenges we had along the way.
First - it was a struggle to find a method to make it visible within AEM if an Asset is already published to Brandportal. The Publish search filter doesn't differenciate between published to AEM and published to BP.
Now we added a pulldown in the metadata schemata, that refers to "./jcr:content/dam:portalReplicationAction" and has the two pulldown options Published (which refers to "Activate") and "Not published (which refers to "Deactivate").
Second struggle was that the connection between AEM and BP has this bug that moving a file within the AEM disconnects the file from its Brand Portal counter. The file stays in Brand Portal, but can't be unpublished any more. Deleting is the only option. 
This is a bit connected with a workflow that we are currently working on. How to make it so, that as soon as a file is updated in any way (changed title, updated version, new metadata entry...) this file then gets also updated within brandportal. Step1 The Launcher checks if the file has an update Step 2 The launcher checks if the file has"./jcr:content/dam:portalReplicationAction" set to activate - then publishes the file again.
Similar workflow had to be build for assets that reached their expiry date.
Biggest Problem so far - still work in progress is - Digital Rights Management.
This works as described within AEM but since the BP is its own repository - and does not have a pipeline connected to it - every license setting we have in /apps/settings/dam/drm/licenses/example.html" or "/conf/company-name/settings/dam/drm/licenses" will not transfer to BP and therefore will not work in BP since the path of the license has to be valid. How to make a valid licence path within BP? Nobody could tell me so far.
I do not want to hijack this conversation - in case somebody wants to see any update on this - here is a link to this specific tread.
Other than that - everyone was very disappointed when it was said that the smart-crops do not transfer as a setting over to BP. Very sad. That leaves only the static renditions, which nobody really needs except the system itself and the Image Presets.
Since it is not possible to create User Groups within B P, there is no real way to make a user group that is able to see Folder A but not Folder B - so it became unusable for "secret" projects, except if the user group is very small and you do not have many secret projects. 
This shrinked the scope and usablilty in a way.
Other than that - most of my struggles with this system come from the fact that i can not deploy settings from my PROD enviroment. I can publish settings, but as soon as i want to edit search rail mimetype predicates, i can either choose to have all 100 filetypes or none. No way to make it slimmer or give it the wording our users would understand. I have created multiple tickets and talked to our consulting agency about these problems.
One thing i have heard is, that Adobe is trying to get a fix for the - moving a file disconnects it - thingy and with a bit of luck will deploy it this year.
I hope i did not spoil to much. I will try to keep this tread updated on any progress.