Talk presenting wireframes and concepts of the upcoming TYPO3 Media Management module and gives an insight into the ongoing development.
Given by Fabien Udriot and Ingmar Schlecht on T3CON11 in Hanau/Frankfurt, Germany.
14. The Project
Metadat
File a
Abstraction
Media RTE
List
Taxono
my
15. File Abstraction
Goals:
• Abstraction between File System and TYPO3
• Integrating files from different sources
• Using Content Delivery Networks (CDNs)
• Clean file access API for Core and
Extensions
39. Current Development
• List Component
• Enables showing grid data
• Advanced filters possible
• Saving and loading of stored filters
• FAL API mostly stable
• Media indexing services
Introducing the team\n\nIngmar:\nLiving in Frankfurt, \nMember of the core team\nCurrently working full time on a TYPO3 core related sponsored project, which this project is part of\n
Requirements:\nFile Abstraction, one part of old DAM, needs to be in the TYPO3 Core\nTherefore, DAM needed to be rebuilt \n
[Intentionally empty slide]\n\nHanding over to Fabien, who will present DAM 1.0\n
\n
\n
\n
\n
\n
\n
FABIEN\n======\nMonolithic architecture -> hard to maintain \nCode basis is obsolete -> less agile\nToo many things are coupled together\nUsability is poor for the End User\n\nConsequence -> it is hard to be sustainable for the Future\n
\nCategorization:\n would be useful for categorizing other records as well\n\nFile referencing:\n Very different way of working with files; Extensions need adoption\n\nList module:\n Has a lot of duplicate code to the core filelist module and the record list module\n Enables advanced searches, which can be saved (unique feature)\n
Goal of this project:\nRebuild the DAM and put the parts that can be re-used in the core\n\nUse the chance to:\nimprove the overall user-experience of Media Management\nuse modern technologies\n\nWhy „media“?\ndam extension key needed for maintenance updates of 1.x\nMore understandable, as it‘s no abbreviation\nPhoenix uses the same term, upwards compatible\n
Seamless integration into the core:\n\nFile Abstraction Layer (more details later)\nFilterable listing engine (re-use for database record listing)\nCategorization by a taxonomy that is used throughout the core\nRTE integration by a unified element browser based on the listing component\nAnd of course: Media itself is also planned as part of the core.\n
Abstraction:\nas an extension developer, you don‘t need to care where the files is stored\n\nIntegration from different sources:\nPossible to write your own „storage driver“.\nConnect to anything from a remote FTP server to external Asset Management Systems\n\nContent Delivery Networks:\nBefore publication, files can be put to CDNs (instead of your local typo3temp/ folder)\n
Two types of storages:\n\n Mounts (for accessing and browsing files in the backend)\n\n Publication Targets (for pushing files to in the Frontend)\n
(this is just a subpart of the total classes)\n(don‘t stay at this slide for long)\n\nFile, Mount and Collection are Domain Model representations of their respective nouns\n\nUnder Service, the storage and indexing architecture can be found.\n\nCurrent state:\n Most parts are relatively stable, but: publication of files for frontend access still missing.\n
\n
Showing usage of a File\n
Listing Engine:\nShow vidi tree browsing\nShow vidi fulltext search\nSave vidi search\nListing engine\nFilters work\nSelections can be saved\nRecord picker\nBackend-side done\nOver\nMedia Management\n
Listing Engine:\nShow vidi tree browsing\nShow vidi fulltext search\nSave vidi search\nListing engine\nFilters work\nSelections can be saved\nRecord picker\nBackend-side done\nOver\nMedia Management\n
Listing Engine:\nShow vidi tree browsing\nShow vidi fulltext search\nSave vidi search\nListing engine\nFilters work\nSelections can be saved\nRecord picker\nBackend-side done\nOver\nMedia Management\n
Listing Engine:\nShow vidi tree browsing\nShow vidi fulltext search\nSave vidi search\nListing engine\nFilters work\nSelections can be saved\nRecord picker\nBackend-side done\nOver\nMedia Management\n
\nFile-related (collected by FAL):\nmodification time, file-type, filename etc.\n\nMedia-related (collected by Media Management):\nimage dimensions, exif data, other metadata\n
Listing Engine:\nShow vidi tree browsing\nShow vidi fulltext search\nSave vidi search\nListing engine\nFilters work\nSelections can be saved\nRecord picker\nBackend-side done\nOver\nMedia Management\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
The project is on Forge, just search for „Media Management“\n
The project is on Forge, just search for „Media Management“\n
\n
Timeline:\n\nFirst working version end of October.\nMore fine-tuning until end of this year.\n\n=> If everything goes as planned, release with TYPO3 4.7 in April.\n
