Has been discussed with Jan-Hendrik from the EAB on 12.02.2013; and has been accepted on 15.02.2013 by the EAB.
(The attached PDF is a snapshot of this work package at the time of acceptance.)

So, Christian, you can schedule this work package in your day-to-day calendar and implement it then -- can't wait to see it in Neos 1.0 :-)

Another side-note: Please do not forget to add comments to this work package and update "% done" while you are working on this package.

Greets, Sebastian

What we show in the mockup and want to do:

- Media files model (need a common base model, images are one example for more specialized models), base behavior include tagging, name, date?
- Tags are hierarchical categories to sort media files into, basically they have just a name. For easier recognition color and icon could be added. Files can be added to multiple tags. Later "smart tags" like smart folder could be implemented that offer files based on preselected criteria. Tags can also be favorited by users for faster access.

There will be two views in the mediabrowser, both share the sidebar and topbar.
Sidebar includes tag hierarchy, favorite tags and common/global actions and links, additionally we need a untagged/unsorted meta-"tag"
Topbar includes actions directly related to files, so a search/filter, operations for selections (like delete selected) and upload
Main view is a more image centric view with thumbnails and alternatively a plain file list (both offer infinite scrolling)

Media files can be added to multiple tags, the "delete" action will remove the file from the currently selected tag! Implement soft delete and implement real deletion later (Only if a file is removed from all tags it can be deleted from the untagged list of files (later on this removal from tags and unconnecting from content could be offered)). To add a file to a tag you drag the file from the list to the tag.
Multiselection of files should be possible together with batch actions on the files.

The scetched application should work standalone and in other application context. To improve interoperability I suggest working only with (RESTful) services so another UI could access functionality as well (think mobile app)

Search for now will be a simple string based filter on the file list, later some more sophisticated filtering can be added.

Files can have actions attached which should be extensible if someone later wants to add more actions.

Questions / Implementation details not yet discussed

Tag sorting/order
Can the application be used in the same way for selecting files and giving selection back to parent application (Neos image content eg.) or do we need a subset as file selector for that?
Sorting in "image view"?

Setting the Due date a bit later as we are behind schedule currently and want to use the Neos sprint for integrating the solution together.