Possible confusing use of Repository Class

[b2m]

The Repository class has the following use cases:

1. Create a new repository and add data
2. Add data to existing repository
3. Read data from existing repository

Let's assume a user wants to read data from an existing repository but requests a wrong path. The Repository Class assumes the user wants to create a new repository and creates it for him. Metaphorically speaking the user is now "waiting" for data from the repository and the repository is "expecting" data from the user. I suspect their needs will not be satisfied :(

The same applies to the second use case: a user wants to add data to an existing repository but accidentally creates a new repository...

To avoid this situation it might be helpful if you could tell the Repository class what you are planning to do. The Repository class will then do it, or tell you that it can't.