Peter,
Thanks for your feedback. The kind of problems which you describe in your message are one of the reasons why I was never keen from a records management point of view on getting involved with SharePoint, Teams, O365, etc.
At the moment what you are talking about is also rather theoretical because I am still trying to have discussion about how we will manage records in Outlook, Teams, etc. with our IT dept. They had been rolling out Outlook in phases at the time, but rolled out Teams with very little notice or preparation in response to all of our employees suddenly having to work from home. I suspect that when I actually begin to work with setting up records management in SharePoint, etc. what you and others have shared will make much more sense. We are lucky that we already have a Lasefiche repository. From what I understand after conversations with our reseller it should be able to help us manage retention of records generated in SharePoint (which in turn manages records in Teams.)
I may come back to you with questions when we start to get specific about managing records with our new tools.
Joseph Coen, C. A.
Archivist
R. C. Diocese of Brooklyn
310 Prospect Park West
Brooklyn NY 11215
Tel.: ;718-965-7300 ext. 1001
Fax 718-965-7302
------Original Message------
Joseph,
I can't answer for Geraldine regarding the other statements she made, but we are grappling with a few governance issues around teams. In terms of channels, there are some people in our organization in favor or restricting the creation of teams and others that want to leave that up to the business. From a records management perspective, Teams leaves a lot to be desired as it lacks the features for manually labelling documents for retention (they're supposed to be planned for a future release) and any planning around content types and metadata needs to be accomplished in the underlying SharePoint site. The nice thing about it is that what you do in SharePoint is reflected in teams, so adding columns, linking document types to folder structures and using managed metadata does appear to come through into the teams UI, but your work will need to be done in SharePoint as there are no features yet to apply labels, fill in column values, etc.
Teams works fine for browsing files and editing documents in place, but otherwise you'll still end up using SharePoint if you have any hope to create a useful information architecture.
Regards
Pete
------------------------------
Peter Rahalski, CIP
Information Solutions Architect
EXCELLUS HEALTH PLANS
------------------------------