Destination-independent item save UI for heterogeneous digital items

Through project storage interface controls and a unified favorites and folder system, the location and platform isolation of digital project storage and access in the productivity suite is solved, unified project management and access is achieved, and user experience and productivity are improved.

CN118901063APending Publication Date: 2024-11-05MICROSOFT TECHNOLOGY LICENSING LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380027506.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-01
Filing Date
2023-01-27
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

Existing productivity suites have location and platform isolation problems when storing and accessing digital projects, resulting in cumbersome user experience and difficulty in uniformly managing and accessing different types of projects.

Method used

Introducing project storage interface controls and a unified favorites and folder system allows users to access and manage digital projects in any context, storing and accessing projects in centralized locations or user-defined folders through project alias.

Benefits of technology

Simplifies user experience, improves productivity, reduces the consumption of computing resources, and reduces network congestion, achieving unified access to different platforms and project types.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901063A_ABST
    Figure CN118901063A_ABST
Patent Text Reader

Abstract

The techniques disclosed herein enable a system to concentrate access to various digital items regardless of the location of these digital items. To accomplish this, items stored at their original location (e.g., within a cloud storage platform) may be selected by a user for storage at a centralized location, such as a favorite portion. The items are selected using an interface control, which may be an operating system component of an item saving system accessible in any context or application. The item conservation system may generate an item alias for the selected item, and then store it in a centralized location. Further, the user may move the item aliases to various destinations to enable custom item storage of items of different types, sources, and locations. In addition, the functionality of the interface control may be modified to accommodate the selected item.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] As computing becomes more and more integrated into the modern workplace, many organizations have equipped their employees with productivity suites to enable viewing, editing, and storage of information. These productivity suites may include several programs or applications that enable users to generate documents, multimedia files, and other digital items from a single main platform. Productivity suites may also enable users to share data between various programs and with other users through online collaboration and remote file storage. Typically, productivity suites may be accessed through computing devices such as desktop computers or laptop computers. Additionally, productivity suites may be accessed by mobile devices such as smartphones and tablet computers.

[0002] The versatility and functionality of modern productivity suites have been greatly expanded through significant investments by service providers. However, users of these productivity suites must contend with an increasing number of applications and project types. For example, a user may utilize one application to store and edit text documents, another application to create a spreadsheet document, yet another application to schedule a meeting with peers, and so on.

[0003] Furthermore, different digital items created by these applications may be stored in different locations (e.g., different network locations and / or different file locations). For example, text documents, spreadsheets, and slide presentations may be stored in one location, while digital design files are stored in another location, and meeting events with peers are stored in another location. Thus, while the various items may all be related to a particular task or project, the user must traverse several separate locations to access the items.

[0004] Furthermore, while some existing solutions allow users to "pin" items to a dashboard or add items to a favorites list, these features are still typically isolated within the immediate context. For example, a file browser may support favorites for various items, but the favorites list is still only accessible through the specific file browser. Similarly, while a web browser may enable a user to bookmark a specific web page, the user must return to the specific web browser to access the bookmark, resulting in a cumbersome and degraded user experience. Therefore, a mechanism is needed to unify project saving at the operating system level to enable users to access saved projects regardless of storage location or platform.

[0005] It is with these and other considerations in mind that the present disclosure is presented herein. Summary of the invention

[0006] The disclosed technology enhances the functionality of an operating system and associated storage systems for digital items such as documents, multimedia files, etc. by introducing bin control and a unified favorites and folder system. Generally speaking, various digital items can be stored at a first location, such as a local file browser, a cloud storage platform, a web browser, etc. A user can select an item to summon an item storage control to select a destination for the item (e.g., a favorites list). An item alias can be stored at the selected destination to enable access to the item regardless of the actual location of the item.

[0007] In various examples, multiple projects can be stored at a first location. For example, projects originating from the same application can be stored together, such as design files or text documents. As will be explained in detail below, a user can select a project to cause a project storage interface control to be displayed. In various examples, an initial selection can cause a project alias associated with the selected project to be stored at a centralized location (e.g., a favorites list). In addition, a user can return to the project to expand the project storage interface control to display additional options for the project and / or project alias.

[0008] Using an additional option, users can store project aliases of selected projects in a custom location (such as a user-defined folder). Thus, project aliases can be deleted from a centralized location and stored in a user-defined folder. For example, a user may want to store all projects associated with a specific project in a folder. Some projects may be stored in an email application, while other projects may be stored in a file explorer, and other projects are stored in a cloud storage platform. Compared to existing solutions, users can utilize project storage interface controls to unify access to projects regardless of the original location of the projects. In this way, the user experience is greatly simplified, thereby improving productivity, saving computing resources, and reducing network congestion.

[0009] Features and advantages other than those explicitly described above will be apparent by reading the following detailed description and reviewing the related drawings. This overview is provided to introduce a selection of concepts in a simplified form, which will be further described in the following detailed description. This overview is not intended to identify the key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. For example, the term "technology" may refer to systems, methods, computer-readable instructions, modules, algorithms, hardware logic, and / or operations as allowed by the context described above and the entire document. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The detailed description will be described with reference to the accompanying drawings. In each figure, the leftmost digit of a reference number indicates the digit in which the reference number first appears. The same reference numbers in different figures represent similar or identical items. References to individual items of a plurality of items may use reference numbers with letters in the alphabetical sequence to refer to each individual item. General references to items may use specific reference numbers without using alphabetical order.

[0011] Figure 1A An example environment is shown in which a system is configured to unify access to digital items through an item storage interface control.

[0012] Figure 1B An example environment is shown in which a user adds selected items to a centralized location.

[0013] Figure 1C An example environment is shown in which the system displays a confirmation for adding selected items to a centralized location and for revealing an expansion element for additional functionality.

[0014] Figure 1D Shown is a centralized location where project aliases can be stored.

[0015] Figure 1E An extended project storage interface control is shown to enable a user to select a custom destination for a project alias associated with a selected project.

[0016] Figure 1F An example environment is shown in which the system displays confirmation for adding selected items to a user-defined folder and an expansion element.

[0017] Figure 1G A destination chooser that may be invoked via a project storage interface control is shown.

[0018] Figure 2 An expanded item storage interface control that exposes a modified set of functions in response to a user selecting a folder is shown.

[0019] Figure 3 An expanded project storage interface control is shown that exposes a modified set of functions based on the project type of the selected project.

[0020] Figure 4 is a block diagram of a system for unifying access to digital items through an item store interface control.

[0021] Figure 5 is a flow chart illustrating aspects of a routine for unifying access to digital items through an item storage interface control.

[0022] Figure 6is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing various aspects of the techniques and technologies presented herein.

[0023] Figure 7 is a schematic diagram illustrating a distributed computing environment capable of implementing aspects of the techniques and technologies presented herein. DETAILED DESCRIPTION

[0024] The technology described herein provides a system for enhancing the management of digital projects by introducing a project storage interface control. Thus, the disclosed system solves several technical challenges associated with unified project preservation across many different platforms and project types. Although some existing solutions may support pinning or collecting projects, they may be limited to certain project types and / or platforms. In contrast, the project storage interface control can be a component of an operating system that is the basis for various applications installed on a user device (e.g., a laptop or tablet). Therefore, the user can access the project storage interface control in any context or application. In this way, the project aliases stored by the disclosed system can also be accessed in any context.

[0025] Furthermore, the disclosed system can greatly simplify human interaction with digital items by enabling unified item saving or storage. As described above, providing access to item storage interface controls in any context can reduce the number of inputs required by the user to reach the desired item. In this way, the disclosed technology can not only support any item type from any platform, but also improve the user experience. Furthermore, by simplifying the user experience in this way, the disclosed system can improve the performance of the computing device by reducing the likelihood of unintentional input, thereby conserving computing resources.

[0026] Reference below Figure 1A-7 Various examples, scenarios, and aspects are described that enable unified access to digital items regardless of location.

[0027] Figure 1AAn example environment 100 is shown in which a user interface 102 displays a set of items 104 for a user to view. The user interface 102 can be part of a cloud storage platform, a local file browser, or any other application that enables a user to view and / or manage various digital items such as documents, events, and folders. For each item 104, the user interface 102 can display a name 106, as well as additional information related to the item 104, such as the time when the item was last opened 108 and the activities 110 associated with the item, which can indicate the source of the item, the most recent action taken on the item, etc. For example, the user interface 102 can indicate that the document (white paper draft 112) was last opened 42 minutes ago 108 and that the user shared the white paper draft 112 in a chat. In addition, the storage location of the item can be displayed as part of the name 106. As shown in FIG. Figure 1A As shown, the same information may be displayed for all projects 104 (eg, budget review 114, idea brainstorming 116, team survey 118, and marketing expo 120).

[0028] Additionally, some of the items 104 may include associated items 122 that may be displayed by the user interface 102. For example, a calendar event representing a marketing expo 120 may have associated items 122, such as meeting notes 124 and sales analysis 126. These associated items 122 may be displayed with the marketing expo 120 to show their association. As will be discussed below, a user may manage the marketing expo 120 along with the associated items 122 as a group using the item storage interface controls.

[0029] As shown on the left side of the user interface 102, various categories of items can be accessed, such as recent items 128, the user's own items or "My Files" 130, a favorites list 132, and shared items 134. In addition, various folders 136 can be displayed on the left portion of the user interface 102 for quick access by the user. In various examples, the user can select certain folders 136 to be displayed in the user interface 102. Alternatively, the folders 136 can be automatically selected based on user activity. For example, if the user frequently accesses the inspiration folder 138, the system can include the inspiration folder 138 as part of the folders 136. In addition, the folders 136 can include locations shared between multiple users. For example, the tiger team folder 140 and the design team folder 142 can be accessed by a group of users and can be selected by the user or the system to be displayed within the user interface 102.

[0030] Now go to Figure 1B, the user can use cursor 144 to select item 104. For example, the user can use cursor 144 or some other user-controlled pointer element (e.g., finger touch) to hover the mouse over white paper draft 112, such as Figure 1B As shown. In response, a selection element 146 and a sharing element 148 may be displayed. In various examples, selecting an item 104 may include clicking on the item 104 with a cursor 144, hovering over the item 104 with the cursor 144, or tapping the item 104 using a touch input from a stylus or other touch device. Selecting the sharing element 148 may enable the user to share the white paper draft 112 with other users. Alternatively, the user may select the selection element 146 to add the white paper draft 112 to the favorites 132. As will be shown and discussed below, the selection element 146 displayed in response to selecting the white paper draft 112 may be considered as the initial or first component of the project storage interface control. In addition, the selection element 146, sharing element 148, or other elements of the user interface 102 may be implemented as selectable interface elements, such as buttons, icons, etc.

[0031] like Figure 1C As shown, in response to activating selection element 146 using cursor 144, a project alias associated with white paper draft 112 can be generated and stored in a centralized location. In one example, the centralized location can be favorites 132. Therefore, the system can display a confirmation 150 indicating to the user that white paper draft 112 has been added to favorites 132. In addition, confirmation 150 can include extension element 152. As will be explained in detail below, activating extension element 152 can enable the user to access additional functions of the project storage interface control. In addition, confirmation 150 can include a link to the current destination of the selected project, as shown by the underline. In this way, the user can quickly navigate to the new destination of white paper draft 112. As described above with respect to selection element 146, confirmation 150 can be similarly viewed as a second element of the project storage interface control.

[0032] Now go to Figure 1D , when items are placed within the favorites 132 section, they can be accessed accordingly within the same user interface 102. For example, Figure 1DAs shown, in response to the user selection of the selection element 146, the white paper draft 112 is now accessible through the favorites 132 section. In one example, the user may have performed a favorite action on the white paper draft 112 on a laptop computer that may have originally stored the white paper draft 112. Now that the white paper draft 112 is placed within the favorites 132 section, it can now be accessed from any device that the user may wish to use. For example, the user may wish to access the white paper draft 112 from a tablet computer at a different location. To convey this functionality to the user, the user interface 102 may include a favorites notification 154. In addition, the favorites notification 154 may indicate that the items 104 within the favorites 132 section can be moved to other folders.

[0033] In various examples, the file data defined by the white paper draft 112 can be moved to the favorites 132 section. Alternatively, as will be explained in detail below, the file data of the white paper draft 112 can be retained at the original storage location, while a project alias representing the white paper draft 112 can be generated. Therefore, the project alias can be stored in the favorites 132 section. In this way, users can save projects 104 from any source without worrying about compatibility of project types or locations, and uniformly access projects 104 from any location or platform.

[0034] Now go to Figure 1E , shows and describes a method in which a user selects Figure 1C . As described above, selecting the expansion element may enable the user to access additional functionality of the item storage interface control 156. For example, the item storage interface control 156 may enable the user to select or choose a specific destination 158 for a selected item 104 or a group of items 104. Figure 1E As shown, the project storage interface control 156 can indicate the current location of the project alias of the white paper draft 112. In this case, the project alias of the white paper draft 112 is currently stored in the favorites 132, as indicated by the check mark or check mark. Subsequently, the user can choose to store the white paper draft 112 in the inspiration folder 138 or the Q2 plan folder 160. Therefore, the project alias of the white paper draft 112 can be removed from the favorites 132 and moved to the inspiration folder 138 or the Q2 plan folder 160.

[0035] Alternatively, the user may select another folder 162. Figure 1GAs shown and discussed, selecting the other folder option 162 may cause additional interface elements to be displayed to enable the user to access further granularity for selecting a destination 158. In addition, the project storage interface control 156 may enable the user to select a priority 164 for the selected project 104. For example, the white paper draft 112 may be assigned a high priority 164. Thus, the white paper draft 112 may be displayed first in various contexts to ensure that the user considers the white paper draft 112 as an important project 104. In addition, the project storage interface control 156 may also enable the user to set a reminder 166 for the selected project 104. In various examples, the reminder 166 may define a specific time (e.g., 3 p.m.) at which the reminder 166 may be displayed to the user. Alternatively, the reminder may define a time interval (e.g., one hour) that elapses before the reminder 166 may be displayed.

[0036] Now go to Figure 1F In response to selecting the Q2 plan folder 160, the user interface 102 may display a folder confirmation 168 indicating that the project alias of the white paper draft 112 is now stored at the selected destination 158. As with the confirmation 150 discussed above, the folder confirmation 168 may include a link to the Q2 plan folder 160 to allow the user to quickly navigate to the selected destination 158. In addition, the folder confirmation 168 may also include an expansion element 152 to enable the user to return to the project storage interface control 156. For example, if the user wishes to change the destination 158 of the white paper draft 112, the expansion element 152 may allow the user to do so with minimal additional input. Alternatively, the user may select multiple folders in which to store the project alias of the white paper draft 112. For example, selecting a destination 158 for a project alias currently stored in the favorites 132 may cause the project alias to be removed from the favorites 132. The disclosed system may also generate multiple instances of a project alias to be stored at multiple corresponding destinations 158. For example, the user may choose to store the white paper draft 112 in the inspiration folder 138 and the Q2 plan folder 160. Alternatively, the user may choose to keep the project alias in the favorites 132 while also selecting a destination 158 to store the project alias, such as the inspiration folder 138. It should be understood that when a destination 158 is selected for the white paper draft 112, the project alias associated with the white paper draft 112 may be stored in the selected destination, while the original location of the white paper draft 112 remains unchanged.

[0037] Now go to Figure 1G, various aspects of a destination interface 170 are shown and described. As described above, the user may choose to select another folder 162 via the item storage interface control 156. In response, the destination interface 170 may be displayed to enable the user to navigate to the specific destination 158 of their choice. Similar to the left portion of the user interface 102, the destination interface 170 may display various locations to which the user may navigate. For example, Figure 1G As shown, the user is currently viewing recent locations 128, as indicated by the bold text and selection indicator. The locations within recent locations 128 may be organized in chronological order based on recent access. From here, the user may select a destination, such as a logo explore folder 172 or a contoso policy folder 174. Thus, an item alias for the selected item 104 may be generated and stored in the logo explore folder 172 for access from any device and / or platform without changing the location of the selected item 104.

[0038] Alternatively, the user may choose to create a new destination 158 using the add here interface element 176. In response, a new destination 158 may be created at the current location viewed by the user. In this example, the current location is the recent location 128, and the new destination 158 may be a folder. In another example, the user may have navigated to a specific location, such as the contoso policy folder 174. By selecting the add here interface element 176, a subfolder may be created within the contoso policy folder 174. It should be understood that a new destination 158 may be created using the add here interface element 176 at any location through the destination interface 170. In addition, the destination interface 170 may enable the user to search for a specific location by name using the search bar 178.

[0039] Now go to Figure 2 , an alternative configuration of the project storage interface control 156 is shown and described. In this case, the user can select the budget review folder 114. Because folders can differ from individual projects 104 in various properties, the project storage interface control 156 can expose a modified set of functions accordingly. For example, the user can still select a destination 158 for the budget review folder 114. In addition, the project storage interface control 156 can also enable the user to pin 202 the budget review folder 114 to the folder portion 136 within the left side of the user interface 102. Therefore, the design review folder 114 can be displayed within the folder portion 136 of the user interface 102. Although Figure 2 A specific example of modified functionality is shown in , but it should be understood that any additional functionality may be automatically added to the project storage interface control 156 in response to selecting a folder rather than an individual project 104 .

[0040] In addition, if Figure 3 As shown, the functionality of the project storage interface control 156 can also be modified based on the project type of the selected project 104. For example, the user can select the final logo design 302, which can be a digital design file. Therefore, the system can detect that the user has selected the final logo design 302 and detect the project type as a digital design file. In response, the project storage interface control 156 can expose a set of functions specific to digital design files. For example, the project storage interface control 156 can detect that the user is part of a design channel within a communication application. Therefore, the project storage interface control 156 can suggest that the user share the final logo design 302 with the design channel 304.

[0041] In another example of modified functionality, the project storage interface control 156 may suggest a destination 158 for the final logo design 302 in response to detecting the project type. For example, the project storage interface control 156 may suggest a design client folder 306. In various scenarios, the project storage interface control 156 may suggest a destination based on the project type, the name of the project, and / or the storage location of the project. For example, the project storage interface control 156 may suggest the design client 306 as a destination 158 based on the project type and the name of the final logo design 302. The system may determine that the final logo design 302 has a certain level of relevance to the design client 306 and suggest a destination accordingly.

[0042] Now go to Figure 4 , additional details of the disclosed system are shown and described that implement various features of the project storage interface control 156. As described above, the project storage interface control 156 can be a component of the operating system 402 that enables a user to access the project storage interface control 156 in any context or application. For example, although the examples described above are shown in the context of a file browser, a user can also use the project storage interface control 156 in a web browser. In one example, a user can highlight a block of text in a web page that they wish to save in the favorites 132. The user can select the block of text, which can cause the operating system 402 to activate the project saving system 404 and display the project storage interface control 156.

[0043] In this example, the block of text may be the selected item 406. In response to the user selecting the item 406, the item storage system 404 may extract various information about the selected item 406. For example, as described above, the item name 408 and the item type 410 may be extracted to inform various aspects of the item storage interface control 156. Additionally, the item quantity 412 may be extracted from the selected item 406. For example, a user may select several items within a file explorer that they wish to store at a certain destination 158.

[0044] Using the various pieces of information extracted from the selected item or group of items 406, the item saving system 404 can configure the item storage interface controls 156. For example, the item saving system 404 can determine one or more suggested destinations 414 based on the item name 408, the item type 410, and / or the number of items 412. In addition, the item saving system 404 can select a suggested application 416 that can view or edit the selected item 406. The selection can be based on the item type 410, for example, in response to detecting an image item type 410, the item saving system 404 can select a photo editing application as the suggested application 416.

[0045] Suggested destinations 414 and suggested applications 416 may be included as part of feature set 418. In addition, the feature set may define various features of the item storage interface control 156 that the user may access for the selected item 406. In various examples, feature set 418 may be some but not all of the features of the item storage interface control 156. For example, although the item preservation system 404 may support sharing of the selected item 406 via the item storage interface control 156, the item preservation system 404 may choose not to enable sharing based on the context derived from the selected item 406. In this way, the item preservation system 404 may select the features most relevant to the selected item 406 and prevent the user from being overwhelmed. However, it should be understood that the item storage interface control 156 may be configured to expose all features for interacting with the selected item 406.

[0046] Once the project preservation system 404 displays the project storage interface control 156 to the user, the user can select the destination 158 at which to save the selected project 406. In response, the project preservation system 404 can generate a project alias 420 representing the selected project 406. In various examples, the project alias 420 can be a shortcut to the selected project 406, which can be stored in an original location different from the destination 158. Alternatively, the project alias 420 can be a copy of the data defined by the selected project 406. For example, a block of text selected from a web page is considered the selected project 406. In this example, the project alias 420 can be a text document including the block of text from the selected project 406. In another configuration, the project alias 420 can be a link to a specific web page from which the block of text originated.

[0047] In another example, the selected project 406 may be a digital design file stored locally on a computing device belonging to the user. However, the user may select a destination 158 that is a shared folder that can be accessed by multiple users over a network connection. Thus, the project alias 420 may be a reconfigured version of the selected project 406 to enable access by other users while keeping the original digital design file at its original location.

[0048] The selection of the type of project alias 420 can be based on various characteristics of the selected project 406. For example, the project alias 420 can be based on the project type 410, wherein large and complex selected projects 406 (such as 3D models) can ensure (warrant) link to the project alias 420 of the selected project 406, rather than copying the selected project 406. On the contrary, the selected project 406 of small size such as text fragments or images can benefit from the project alias 420, which copies the data defined by the selected project 406 to minimize loading time or other delays. In various examples, the project alias 420 can be configured by the project preservation system 404 based on the selected project 406. It should be understood that the project alias 420 can be any format that enables the selected project 406 to be stored in the selected destination 158, regardless of the original location of the selected project 406. In addition, the project alias 420 can be accessed from any device or platform configured with the project preservation system 404 as a component of the operating system 402.

[0049] Additionally, the project preservation system 404 can be a component of the project preservation service 422. In various examples, the project preservation service 422 can be provided as a cloud service to enable unified storage and access to the project aliases 420. Access to the project preservation system 404, and therefore access to the project storage interface controls 156, can be managed through subscriptions or other forms of access to the project preservation service 422. For example, a user can interact locally with the project preservation system 404 as a component of the operating system 402 via a computing device 424. However, if the computing device 424 is not connected to the project preservation service 422, the user may be prevented from using some or all of the features of the project preservation system 404.

[0050] Now go to Figure 5 , various aspects of a routine 500 for implementing unified access to items regardless of the original location are shown and described. For ease of understanding, the processes discussed in the present disclosure are described as separate operations represented as independent blocks. However, these separately described operations should not be interpreted as necessarily order-dependent for their performance. The order in which the process is described is not intended to be interpreted as a limitation, and any number of the described process blocks may be combined in any order to implement the process or an alternative process. In addition, one or more of the provided operations may be modified or omitted.

[0051] The specific implementation of the technology disclosed herein is a selection problem that depends on the performance of the computing device and other requirements. Therefore, the logical operations described herein are referred to as states, operations, structural devices, actions or modules in different ways. These states, operations, structural devices, actions and modules can be implemented in hardware, software, firmware, special digital logic and any combination thereof. It should be understood that more or less operations than those shown in the figure and described herein can be performed. These operations can also be performed in a different order than described herein.

[0052] It should also be understood that the methods shown can be terminated at any time and do not need to be performed in full. Some or all of the operations of these methods and / or substantially equivalent operations can be performed by executing computer-readable instructions included on a computer storage medium, as described below. The term "computer-readable instructions" and its variants as used in the specification and claims are widely used herein to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, etc. Computer-readable instructions can be implemented on various system configurations, including single-processor or multi-processor systems, minicomputers, mainframe computers, personal computers, handheld computing devices, microprocessor-based programmable consumer electronics, combinations thereof, etc.

[0053] Therefore, it should be understood that the logical operations described herein are implemented as (1) a sequence of computer-implemented actions or program modules running on a computing system and / or (2) interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice depending on the performance and other requirements of the computing system. Therefore, the logical operations described herein are variously referred to as states, operations, structural devices, actions, or modules. These operations, structural devices, actions, and modules can be implemented in software, firmware, dedicated digital logic, and any combination thereof.

[0054] For example, the operation of routine 500 is described herein as being implemented at least in part by a module that runs features disclosed herein, which may be a dynamic link library (DLL), a static link library, a function generated by an application programming interface (API), a compiler, an interpreter, a script, or any other executable instruction set. Data may be stored in a data structure in one or more memory components. Data may be retrieved from a data structure by addressing a link or reference to the data structure.

[0055] Although the following diagrams relate to the components of the accompanying drawings, it should be understood that the operation of routine 500 can also be implemented in many other ways. For example, routine 500 can be implemented at least in part by a processor or local circuit of another remote computer. In addition, one or more operations of routine 500 can be implemented alternatively or additionally at least in part by a chipset that works alone or in combination with other software modules. In the example described below, one or more modules of the computing system can receive and / or process the data disclosed herein. Any service, circuit or application suitable for providing the technology disclosed herein can be used in the operation described herein.

[0056] Reference Figure 5 , the routine 500 begins at operation 502, where the system stores a plurality of items at a first location.

[0057] Next, at operation 504, the system receives a user selection of an item from a plurality of items at a first location.

[0058] Then, at operation 506 , the system displays a project storage interface control in response to the user selection of the project.

[0059] Subsequently, at operation 508 , the system receives a first user input at the item storage interface control indicating a selected item for storage at the centralized location.

[0060] Then, at operation 510 , in response to the first user input, the system generates a project alias associated with the selected project.

[0061] Next, at operation 512, the system stores the project aliases at a centralized location regardless of the first location of the selected project.

[0062] Then, at operation 514, the system receives a second user input at the project storage interface control selecting a user-defined location other than the centralized location for storing the project.

[0063] Next, at operation 516 , in response to the second user input, the system removes the project alias from the centralized location.

[0064] Finally, at operation 518, the system stores the project alias at a user-defined location.

[0065] Figure 6 Additional details of an example computer architecture 600 of a device capable of executing computer instructions (eg, modules or program components described herein), such as a computer or server configured as part of the cloud-based platform or system 100 , are shown. Figure 6 The computer architecture 600 shown in includes a processing unit 602 , a system memory 604 (including random access memory 606 (“RAM”) and read only memory (“ROM”) 608 ), and a system bus 610 that couples the memory 604 to the processing unit 602 .

[0066] A processing unit (e.g., processing unit 602) may represent, for example, a CPU-type processing unit, a GPU-type processing unit, a field programmable gate array (FPGA), another type of digital signal processor (DSP), or other hardware logic components that may be driven by a CPU in some cases. For example, but not limited to, illustrative types of hardware logic components that may be used include application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), etc.

[0067] The ROM 608 stores a basic input / output system containing the basic routines that help transfer information between elements within the computer architecture 600, such as during startup. The computer architecture 600 also includes a mass storage device 612 for storing an operating system 614, applications 616, modules 618, and other data described herein.

[0068] The mass storage device 612 is connected to the processing unit 602 through a mass storage controller connected to the bus 610. The mass storage device 612 and its associated computer-readable media provide non-volatile storage for the computer architecture 600. Although the description of computer-readable media contained herein refers to mass storage devices, those skilled in the art will appreciate that computer-readable media can be any available computer-readable storage media or communication media that can be accessed by the computer architecture 600.

[0069] Computer-readable media may include computer-readable storage media and / or communication media. Computer-readable storage media may include one or more of volatile memory, non-volatile storage and / or other persistent and / or secondary computer storage media, removable and non-removable computer storage media, implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules or other data. Thus, computer storage media includes media in tangible and / or physical form included in devices and / or hardware components that are part of a device or external to a device, including but not limited to random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), phase change memory (PCM), read only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disk read-only memory (CD-ROM), digital versatile disks (DVD), optical cards or other optical storage media, magnetic cassettes, magnetic tape, magnetic disk storage, magnetic cards or other magnetic storage devices or media, solid-state memory devices, storage arrays, network attached storage, storage area networks, hosted computer storage, or any other storage memory, storage device, and / or storage medium that can be used to store and maintain information for access by a computing device.

[0070] In contrast to computer-readable storage media, communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal (such as a carrier wave) or other transmission mechanism. As defined herein, computer storage media does not include communication media. That is, computer-readable storage media itself does not include communication media consisting only of a modulated data signal, a carrier wave, or a propagation signal.

[0071] According to various configurations, the computer architecture 600 can operate in a networked environment using logical connections to remote computers through a network 620. The computer architecture 600 can be connected to the network 620 via a network interface unit 622 connected to the bus 610. The computer architecture 600 can also include an input / output controller 624 for receiving and processing input from a number of other devices, including a keyboard, a mouse, a touch screen, or an electronic stylus or pen. Similarly, the input / output controller 624 can provide output to a display screen, a printer, or other type of output device.

[0072] It should be understood that when loaded into processing unit 602 and executed, the software components described herein can convert processing unit 602 and the entire computer architecture 600 from a general-purpose computing system to a customized special-purpose computing system to facilitate the functions presented herein. Processing unit 602 can be composed of any number of transistors or other discrete circuit elements, which can present any number of states individually or together. More specifically, processing unit 602 can operate as a finite state machine in response to executable instructions contained in the software modules disclosed herein. These computer executable instructions can convert processing unit 602 by specifying how processing unit 602 converts between states, thereby converting transistors or other discrete hardware elements that constitute processing unit 602.

[0073] Figure 7 An illustrative distributed computing environment 700 capable of executing the software components described herein is depicted. Figure 7 The distributed computing environment 700 shown in can be used to execute any aspects of the software components presented herein. For example, the distributed computing environment 700 can be used to execute various aspects of the software components described herein.

[0074] Thus, the distributed computing environment 700 may include a computing environment 702 operating on, communicating with, or being part of a network 704. The network 704 may include various access networks. One or more client devices 706A-706N (hereinafter collectively and / or generally referred to as "clients 706", and also referred to herein as computing devices 706) may communicate with the computing environment 702 via the network 704. In one illustrated configuration, the client 706 includes a computing device 706A, such as a laptop computer, desktop computer, or other computing device; a tablet computer or tablet computing device ("tablet computing device") 706B; a mobile computing device 706C, such as a mobile phone, smart phone, or other mobile computing device; a server computer 706D; and / or other devices 706N. It should be understood that any number of clients 706 may communicate with the computing environment 702.

[0075] In various examples, computing environment 702 includes server 708, data store 610, and one or more network interfaces 712. Server 708 can host various services, virtual machines, portals, and / or other resources. In the configuration shown, server 708 hosts virtual machine 714, portal website 716, mailbox service 718, storage service 720, and / or social networking service 722. Figure 7 As shown, server 708 may also host other services, applications, portals, and / or other resources (“other resources”) 724 .

[0076] As described above, the computing environment 702 may include a data store 710. According to various implementations, the functionality of the data store 710 is provided by one or more databases operating on or in communication with the network 704. The functionality of the data store 710 may also be provided by one or more servers that are configured to host data for the computing environment 700. The data store 710 may include, host, or provide one or more real or virtual data stores 726A-726N (hereinafter collectively and / or generally referred to as "data storage 726"). The data store 726 is configured to host data used or created by the server 808 and / or other data. That is, the data store 726 may also host or store web documents, word documents, presentation documents, data structures, algorithms for execution by the recommendation engine, and / or other data used by any application. Various aspects of the data store 726 may be associated with a service for storing files.

[0077] The computing environment 702 can communicate with or be accessed by a network interface 712. The network interface 712 can include various types of network hardware and software for supporting communication between two or more computing devices, including but not limited to computing devices and servers. It should be understood that the network interface 712 can also be used to connect to other types of networks and / or computer systems.

[0078] It should be understood that the distributed computing environment 700 described herein can provide any number of virtual computing resources and / or other distributed computing functions for any aspect of the software elements described herein, which can be configured to perform any aspect of the software components disclosed herein. According to various implementations of the concepts and technologies disclosed herein, the distributed computing environment 700 provides the software functions described herein as services to computing devices. It should be understood that computing devices can include real or virtual machines, including but not limited to server computers, network servers, personal computers, mobile computing devices, smart phones and / or other devices. Therefore, various configurations of the concepts and technologies disclosed herein enable any device configured to access the distributed computing environment 700 to utilize the functions described herein to provide the technology disclosed herein and other aspects.

[0079] The disclosure presented herein also includes the subject matter set forth in the following clauses.

[0080] Example Clause A: A method includes: storing multiple items at a first location; receiving a user selection of an item from the multiple items; displaying an item storage interface control in response to the user selection of the item; receiving a first user input at the item storage interface control, the first user input indicating a selected item from the multiple items to be stored at a centralized location; generating an item alias associated with the selected item in response to the first user input; storing the item alias at the centralized location regardless of the first location of the selected item; receiving a second user input at the item storage interface control, the second user input selecting a user-defined location different from the centralized location; removing the item alias from the centralized location in response to the second user input; and storing the item alias at the user-defined location.

[0081] Example clause B: The method of example clause A, wherein the centralized location is a predetermined default project location.

[0082] Example Clause C: A method according to Example Clause A or Example Clause B, wherein the user-defined folder stores multiple project aliases, each of the multiple project aliases is associated with a project stored at a location different from the user-defined folder.

[0083] Example clause D: The method of any of example clauses A to C, wherein the plurality of items at the first location originate from the same application.

[0084] Example clause E: A method according to any one of example clauses A to D, wherein the function of the project storage interface control is determined based on the name of the selected project.

[0085] Example clause F: A method according to any of example clauses A to E, wherein the functionality of the item storage interface control is modified in response to user input selecting two or more items of the plurality of items.

[0086] Example clause G: A method according to any one of example clauses A to F, wherein the project storage interface control is an operating system component for centrally storing project aliases.

[0087] Example Clause H: The method according to any one of Example Clauses A to G also includes: detecting an item type of the selected item; and in response to detecting the item type of the selected item, displaying one or more suggested user-defined locations within the item storage interface control based on the item type.

[0088] Example Clause I: A system comprises: one or more processing units; and a computer-readable medium having computer-readable instructions encoded thereon, which, when executed by the one or more processing units, cause the system to perform the following operations: store multiple items at a first location; receive a user selection of an item from the multiple items; in response to the user selection of the item, display an item storage interface control; receive a first user input at the item storage interface control, the first user input indicating that the selected item from the multiple items is to be stored at a centralized location; in response to the first user input, generate an item alias associated with the selected item; store the item alias at the centralized location regardless of the first location of the selected item; receive a second user input at the item storage interface control, the second user input selecting a user-defined location different from the centralized location; in response to the second user input, delete the item alias from the centralized location; and store the item alias at the user-defined location.

[0089] Example Clause J: A system according to Example Clause I, wherein the project storage interface control is an operating system component for centrally storing project aliases.

[0090] Example Clause K: A system according to Example Clause I or Example Clause J, wherein the user-defined folder stores a plurality of project aliases, each of the plurality of project aliases being associated with a project stored at a location different from the user-defined folder.

[0091] Example clause L: A system according to any of example clauses I to K, wherein the function of the project storage interface control is determined based on the name of the selected project.

[0092] Example clause M: A system according to any of example clauses I to L, wherein the functionality of the item storage interface control is modified in response to user input selecting two or more items of the plurality of items.

[0093] Example Clause N: A system according to any one of Example Clauses I to M, wherein the computer-readable instructions further cause the system to: detect an item type of a selected item; and in response to detecting the item type of the selected item, display one or more suggested user-defined locations within the item storage interface control based on the item type.

[0094] Example Clause O: A computer-readable storage medium having computer-readable instructions encoded thereon, which, when executed by a system, cause the system to perform the following operations: store multiple items at a first location; receive a user selection of an item from the multiple items; in response to the user selection of the item, display an item storage interface control; receive a first user input at the item storage interface control, the first user input indicating a selected item from the multiple items to be stored at a centralized location; in response to the first user input, generate an item alias associated with the selected item; store the item alias at a centralized location regardless of the first location of the selected item; receive a second user input at the item storage interface control, the second user input selecting a user-defined location different from the centralized location; in response to the second user input, delete the item alias from the centralized location; and store the item alias at the user-defined location.

[0095] Example clause P: A computer-readable medium according to example clause O, wherein the project storage interface control is an operating system component for centrally storing project aliases.

[0096] Example clause Q: A computer-readable medium as described in example clause O or example clause P, wherein the function of the project storage interface control is determined based on the name of the selected project.

[0097] Example Clause R: A computer-readable medium according to any one of Example Clauses O to Q, wherein the user-defined folder stores multiple project aliases, each of the multiple project aliases is associated with a project stored at a location different from the user-defined folder.

[0098] Example Clause S: ​​A computer-readable medium according to any of Example Clauses O to R, wherein the functionality of the item storage interface control is modified in response to user input selecting two or more items of the plurality of items.

[0099] Example clause T: A computer-readable medium according to any one of example clauses O to S, wherein the computer-readable instructions further cause the system to perform the following operations: detect an item type of a selected item; and in response to detecting the item type of the selected item, display one or more suggested user-defined locations within the item storage interface control based on the item type.

[0100] Although certain example embodiments have been described, these embodiments have been presented by way of example only and are not intended to limit the scope of the inventions disclosed herein. Therefore, nothing in the foregoing description is intended to imply that any particular feature, characteristic, step, module, or block is necessary or indispensable. In fact, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions, and changes may be made in the form of the methods and systems described herein without departing from the spirit of the inventions disclosed herein. The appended claims and their equivalents are intended to cover forms or modifications that would fall within the scope and spirit of certain inventions of the inventions disclosed herein.

[0101] It should be understood that any references to “first”, “second”, etc. elements in the summary and / or detailed description are not intended to and should not be interpreted as necessarily corresponding to any references to the “first” and “second”, etc. elements of the claims. On the contrary, any use of “first” and “second” in the summary, detailed description, and / or claims can be used to distinguish between two different instances (e.g., two different files) of the same element.

[0102] Finally, although various configurations have been described using language specific to structural features and / or methodological acts, it should be understood that the subject matter defined in the appended representations is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed subject matter.

Claims

1. A method comprising: storing a plurality of items at a first location; receiving a user selection of an item from the plurality of items; In response to said user selection of said item, displaying an item storage interface control; receiving, at the project storage interface control, a first user input indicating a selected project of the plurality of projects to be stored at a centralized location; In response to the first user input, generating a project alias associated with the selected project; storing the project aliases at the centralized location regardless of the first location of the selected project; receiving, at the project storage interface control, a second user input selecting a user-defined location different from the centralized location; Responsive to the second user input, removing the project alias from the centralized location; as well as The project alias is stored in the user-defined location.

2. The method according to claim 1, wherein: The centralized location is a predetermined default project location.

3. The method according to claim 1, wherein: The user-defined folder stores a plurality of project aliases, each of the plurality of project aliases being associated with a project stored at a location different from the user-defined folder.

4. The method according to claim 1, wherein: The plurality of items at the first location originate from the same application.

5. The method according to claim 1, wherein: The function of the project storage interface control is determined based on the name of the selected project.

6. The method according to claim 1, wherein: The functionality of the item storage interface control is modified in response to user input selecting two or more items of the plurality of items.

7. The method according to claim 1, wherein: The project storage interface control is an operating system component used for centrally storing project aliases.

8. The method according to claim 1, further comprising: Detect the project type of the selected project; as well as In response to detecting the item type of the selected item, one or more suggested user-defined locations are caused to be displayed within the item storage interface control based on the item type.

9. A system comprising: one or more processing units; as well as A computer-readable medium having computer-readable instructions encoded thereon, the computer-readable instructions, when executed by the one or more processing units, causing the system to: storing a plurality of items at a first location; receiving a user selection of an item from the plurality of items; In response to said user selection of said item, displaying an item storage interface control; receiving, at the project storage interface control, a first user input indicating a selected project of the plurality of projects for storage at a centralized location; In response to the first user input, generating a project alias associated with the selected project; storing the project aliases at the centralized location regardless of the first location of the selected project; receiving, at the project storage interface control, a second user input selecting a user-defined location different from the centralized location; Responsive to the second user input, removing the project alias from the centralized location; as well as The project alias is stored in the user-defined location.

10. The system according to claim 9, wherein: The project storage interface control is an operating system component used for centrally storing project aliases.

11. The system according to claim 9, wherein: The user-defined folder stores a plurality of project aliases, each of the plurality of project aliases being associated with a project stored at a location different from the user-defined folder.

12. The system according to claim 9, wherein: The function of the project storage interface control is determined based on the name of the selected project.

13. The system according to claim 9, wherein: The functionality of the item storage interface control is modified in response to user input selecting two or more items of the plurality of items.

14. The system according to claim 9, wherein: The computer readable instructions further cause the system to: detecting the item type of the selected item; and In response to detecting the item type of the selected item, one or more suggested user-defined locations are caused to be displayed within the item storage interface control based on the item type.

15. A computer-readable storage medium having computer-readable instructions encoded thereon, the computer-readable instructions, when executed by a system, causing the system to: storing a plurality of items at a first location; receiving a user selection of an item among the plurality of items; In response to said user selection of said item, displaying an item storage interface control; receiving, at the project storage interface control, a first user input indicating a selected project of the plurality of projects for storage at a centralized location; In response to the first user input, generating a project alias associated with the selected project; storing the project aliases at the centralized location regardless of the first location of the selected project; receiving, at the project storage interface control, a second user input selecting a user-defined location different from the centralized location; Responsive to the second user input, removing the project alias from the centralized location; as well as The project alias is stored in the user-defined location.