Apps

Infinite scroll view so that events can easily bleed into other months
Ability to define non-work days so that events won't be scheduled into them when they're moved around
Event types so that different departments can be tracked with different colors
Event links so that things that depend on each other behave as they should

All long-term processes should create a new event post with the name of the process, author of the event, the time it started, and any other relevant information
The process should update the post with an end time once the process is terminated

Page that shows the tags or properties that should be applied to all the assets in the batch and allows the the user to browse to the server folder that should be scanned
Preliminary scan populates a page with the found assets and fills out their names, the predefined tags, and any additional tags created by analyzing the name or path. The preliminary scan will save this information on the node endpoint because the asset endpoint requires checksums.
The user may add any additional tags on this page as they see fit
Once the scan completes, the newly-created assets are assigned the given tags and properties and the preliminary information is deleted.

Convert videos to the appropriate HTML5 video format
Allow users to play, pause, and scrub the video
'Add note' button converts the cursor to a drawing tool and opens a text box for notes
'End note' button takes a screenshot of the current frame, overlays the note information, and saves the text, the frame number, and any other relevant information

Components

For any displayable image (preferably in large formats, not thumbnails), click an overlay button to enter tagging mode
Clicking on the image will create an image tag and pop up a window where users can enter text tags to associate with it
Tags added this way will create an image-tag key in the content field that has the coordinates of the tag and the associated text tags. Text tags will also be added to the content field separately.

Channels for assets, each of the node types, batch processes, and discussions.
On every write to the database, Eve sends a ping to an event processor with details about the change
Event processor pushes information to the appropriate channels. This is like a pre-pub/sub that's used by apps that don't know what channel to talk to.
Subscribers of those channels react to information as it comes in