Hello,
We’re building a state service portal that gives a set of permission documents by a request. I’d like you to suggest better information architecture based on SharePoint lists, columns and content types.
There are 30 types of requests from child adoption to building a house. Every request can be sent by either a person or an organization. So every request should contain a block of fields about the author (person or/and organization). However, depending on the type, a request also contains a unique block of fields that describes the object of the request (f.e. a construction site address, or some info about a child to adopt, or some params of a building to construct). The requests then are counted different in statistics reports, like how many were approved, denied or being in work and so on. The requests are also grouped by their statuses and categories (like “my requests”, “requests assigned to me”
So now I’m thinking about how to organize the architecture of this information in a better way. Do you have any ideas?
Wow, nothing like a bit of SharePoint complexity to set the heart racing! Some good thinking in those solutions.
The key point that I can see is that variant 2 has one main list (with the 30 content types). This would be easier to control, create views and report on. Content types being specific for each request are easier to update and change if required. I have used content types for different forms, in terms of containing all the required fields (in this case your request form) and it works well especially for creating web forms and workflows.
You might have to build a mini version for testing without creating all the content types.
Hope that helps Michael.
