Mary wants her laptop to carry all of her documents for work and some of her music, but doesn’t have enough space for all of her music on her laptop.
James wants to make sure that his 80Gb Digital Music Player has all of his most listened to tracks, but also wants to sync his contacts and his calendar to the device along with some of his most important notes.
As well as being able to specify sync priorities with Data Storage and Organisation enabled devices Data Storage and Organisation can also use foreign sync plugins in collaboration with conduit to synchronise with non-Data Storage and Organisation enabled devices. Metadata can be used to build up detailed priority lists based on parameters like, your favourite music, the storage capacity of the device, and other any other requirements.
David has created 2 copies of his buisiness plan. One copy includes what he considers to be a more risky part of the business plan and therefore wants to keep that as an idea on the back burner while he presents to the bank a preliminary plan which carries less risk.
With Data Storage and Organisation you’ll be able to name branches of your files, simply by creating a file, then branching from the version you’d like to create variations of, then specifying the name of the different versions. A three way merge can be performed later.
Susan, Paul and Jason are collaborating on a document. Susan is in the office and Paul is sometimes in the office, sometimes on the road, Jason is a remote worker and will be in any number of places throughout the day in various timezones. Merging should happen whenever possible, and one of the three could be nominated to perform the merge. In this case Susan would be the best choice as she is in the office normal business hours and can see changes coming in from both sides more regularly.
Data Storage and Organisation creates a distributed revision control system which is like a mist. As devices enter and exit that mist they will communicate a full set of changes, merges can take place automatically in some cases, and manually in others
Browsing heaps of data
Henry has a lot of documents, letters and mailings. He’s torn between where he puts his files at times. Looking into his documents folder he has a folder for all of his financial documents, and a folder for all of his letters. In once instance he decides to put a letter to his bank into the letters folder. In the future he has trouble finding it.
Large file systems are generally difficult to navigate, deep file systems specify too much and can end up hiding data, wide file systems tend to be too generalised and still require hunting and foraging for the file name, and requiring some memory of what that represents. With a semantic file system what we have is a file system designed to have many paths to desired data, the file system is both wide and deep but there are many ways to find what you are looking for, one path doesn’t necessarily close off other paths.