Any SharePoint gurus out there? Let's say you have a function but it's spread across district offices all over the country. Whilst each district office has it's own data, they all group their data in a similar way: the north area will have an admin team, the same as the east team. The structure is the same in each district, but the data in each team will generally only relate to the district office.
So, do you build a site collection based on the district offices, thus replicating multiple document libraries that all house similar data but are divided up. Or build a site collection based on the same work areas for each district and then spilt out to each district below that?
In terms of the number of document libraries, number of clicks, etc. You're overall nav journey isn't any more difficult either way. But it does seem odd to replicate the same structure across multiple sites for multiple districts, when actually the work they all do is the same.
This must be a very common issue (any organisation that has more than 1 office!) but it's surprising difficult to find any guidance on this topic. My instincts are telling me that grouping all the admin data together on the same site/page would the best approach as all the admin teams could then collaborate. But on the other hand local offices do tend to be very focused on their own Idaho.
To view the list archives go to: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=RECORDS-MANAGEMENT-UK
To unsubscribe from this list, send an email to [log in to unmask] with the words UNSUBSCRIBE RECORDS-MANAGEMENT-UK
For any technical queries re JISC please email [log in to unmask]
For any content based queries, please email [log in to unmask]
|