Abstract: An “asset-based” user interface can be provided based on consulting metadata with an asset and presenting an interface to allow selection of actions associated with that particular asset. By presenting a listing of actions in response to a single command, the user can be spared the need to navigate through contextual menus to determine available services. The interface can be presented in a file selection interface provided by an operating system, e.g., in response to an “open” command in a folder. A method can comprise identifying a command referencing an asset and accessing metadata associated with the asset. The accessed metadata can comprise a unique metadata record for the asset available locally and/or accessible from a remote computing system. The method may further comprise determining one or more actions available for use with the referenced asset and providing an interface for selecting one or more of the determined actions.

Abstract: An “asset-based” user interface can be provided based on consulting metadata with an asset and presenting an interface to allow selection of actions associated with that particular asset. By presenting a listing of actions in response to a single command, the user can be spared the need to navigate through contextual menus to determine available services. The interface can be presented in a file selection interface provided by an operating system, e.g., in response to an “open” command in a folder. A method can comprise identifying a command referencing an asset and accessing metadata associated with the asset. The accessed metadata can comprise a unique metadata record for the asset available locally and/or accessible from a remote computing system. The method may further comprise determining one or more actions available for use with the referenced asset and providing an interface for selecting one or more of the determined actions.