Running Notes

My situation: my customer is looking to implement Quickr as a document management system (among other things, but this is first priority). The current system consists of a server drive with folder and subfolders. I’m looking for input on the best Quickr implementation.

Let’s call the server “Fruit”. There are two main folders, “Apples” and “Oranges”. Within both Apples and Oranges, there are subfolders. Apples contains “McIntosh”, “Granny Smith”, “Fuji”, “Rome”, etc. There are various folders and documents within each of those. Same goes for Oranges, there are subfolders, “Navel”, “Valencia”, etc.

So my question is whether Apples and Oranges should be Quickr places, and McIntosh and Navel should be rooms within those places, or if McIntosh and Navel should be places of their own? What are considerations for either way of setting it up?

With over 300 types of apples, we’d rather get this right on the first try. I’ve done a bit of searching around (admittedly, not a lot) and not found anything regarding a Best Practice for the architecture of a Quickr server.

I realize we can use tagging and such to categorize documents, so that will eliminate some of the need for “folders”, particularly, I am thinking the subfolders within each variety (Navel) will be unnecessary.

My first instinct is to create a place for each variety. Creating more places with fewer documents, rather than a few places with loads of documents. However, I am not a Quickr expert, and so turn to the “Yellow-verse” for your opinions.

We will need to search across all Apples. I’m not entirely sure if that makes a big difference.

Don’t be too hard on me, remember I’m a dev, not a Quickr Implementation Specialist! My admins don’t have blogs, so I’m asking the question on their behalf. Anyway, I’d love to hear your thoughts/experiences. Or feel free to tell me I am a moron, and show me a link.