You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Future

External AssetProviders

Currently we are only focused on the DAM AssetProviderType. The topic of additional AssetProviders is complicated. But we collect some thoughts here for now.

Brainstorming possible AssetProviderTypes

  • Another workspace - ie "data" from Data module.
  • Dropbox
  • Flicker
  • S3
  • Akamai
  • Google drive

What are the External provider use cases?

  • I have a big collection of assets that I want to use on my site - i dont care where they are served, i just want to use them comfortably.
  • I have a big collection of assets in a nice asset system that I will continue to use - I dont want to manage assets in magnolia's low-end dam system. But I would like to select assets from my system for use on pages.
  • There are a few assets in another dam system that i want to use - i could import them.
  • I want to serve some CDN hosted assets on my website.
    • I already have a bunch of CDN assets that I would like to select and use.
    • I would just like to have all of my website assets uploaded and served from a CDN. (Akamai and a CMS comments http://forums.adobe.com/message/4804400)
  • I have a video on youtube, vimeo etc that I would like to serve.

Conclusions based on above use cases

  1. It does not make sense to provide an asset from a CDN, because we create renditions of those and store those locally. A CDN implementation is something that should be applied afterwards.

DAMHandler & STK DAM Integration

  • How does the UI look if I add additional DAMHandlers
    • Tabs for various options to upload images?

Problems

  • Imaging module cannot work with an external asset on s3, flickr, akamai - if you want it served from there.
    • The point of these locations is that they store and serve the asset that you want to use. If you resize and store it locally, then that defeats the purpose.
    • I guess imaging module is still useful for adminCentral uses: thumbnails / 

(Unimplemented) Concept for Configuration of AssetProviders

  • DAM
    • config
      • providers
        • dam1
          • class = info.magnolia.dam.providers.dam 
          • assetBrowserLabel = Dam
        • dropbox1
          • class = info.magnolia.dam.providers.dropbox
          • bucket = startrekmemories
          • authUserName = wil.wheaton
          • authKey = YR&#*YRHUHRU#HR#HR
          • assetBrowserLabel = Dropbox Wil.Wheaton

TODO

Further TODO

  • Add upload to the Asset Browser.
  • Create the Provider Registry
  • Add provider options (from the registry) to the Asset Browser.
  • Use Case: have two different dam workspace provider instances to the Asset Browser.
  • Extra Credit: s3 or dropbox provider
  • No labels