Abstract: A method and system are provided for automatic workflow versioning. A workflow database can include metadata describing the relationships between data files, a workflow association and version/timestamp information such that relationships can be tracked against time and file versions. A system is provided to visualize a workflow and how it changes over time. A workflow navigator can be provided to allow a user to graphically “slide” back and forth in time between different workflow versions or points. Date/Time stamp information can be displayed and the workflow relationships and graphical thumbnails can change as the user hits dates/times where changes occurred. Further controls can be provided that allow the user to choose a previous version of a workflow from the timeline, and to bring forward in time the associated files and relationship information.

Abstract: A method and system are provided for browsing assets stored in memory in a computing environment. Asset interdependence is used as a central model for organizing and displaying assets in an asset map. The asset map is a visual representation an asset of interest and a set of assets having a logical usage relationship with the asset of interest. The asset map preferably concurrently shows the related assets, their relationships, and a location of the assets on storage media in the computing environment. The assets are shown as nodes on a map with visual indicators describing relationships between them. Component assets are shown as assets used in an asset of interest, and output assets are shown as outputs generated using the asset of interest. These assets, or data entities, include applications, files, folders, fonts, effects, image layers, animation compositions, video tracks, and audio tracks.

Abstract: A method and system are provided to automatically and transparently version files across many desktop applications without requiring the user to take specific action to cause the versioning to occur. Previous versions and versioning information can both be stored using hard links, and the versioning information can be used to determine a version history for a file. Embodiments of the present invention do not require applications to be modified to support this versioning method. Further, using one approach, the application does not even know that the versioning is occurring. The present invention provides an automatic versioning solution that is completely transparent to the user, which causes overwrite operations to be seamlessly co-opted into versioning operations which retain previous document versions instead of overwriting them.