Quote:
Originally posted by armsys
Just imagine mixing Info Items on R&D, tech support, marketing & sales, to-do lists, travel plan, lecture notes, readings,...etc.
|
I guess it becomes a question of scale. If these areas of interests (categories or departments) were from the perspective of an individual contractor, then structuring a single database could probably handle the divergent tasks. Even scaling this to a small office could work. If we're talking different departments within a company, then you may have to look at different urds for each department.
The suggestion of creating Templates for most of your needs will help to focus searching for divergent types of Items.
For example, you have a category R&D which lends itself to being a parent whose children are Projects. Create a Template for this Project Item, base it on the Text Template, create some Attributes that describe and allow you to track the Project, create a Form for these (and/or other) Attributes and the assign the Form to the Project Template.
Perhaps a Project has a standard group of tasks, if you can get by using the default Task Template use it as the basis for each of the required tasks. You could then build a new nested template from these individuals. The Default Template for nested_Project could be the default Task Template (or something else).
Create a folder off the root for R&D, it's Default Template could be the nested_Project Template above.
Because each of these Items is based on a specific Template, this becomes a condition in your search, the state of other Attributes for an Item can be further specified in the search.
Something else to consider is that UR can map Windows File Properties, if you're using MS Office and have this Summary Information setup it can be a real time saver.
I am also curious as to how others approach these problems.