Information architecture & information management for group files
Part of a much bigger concern customers are voicing: the disappearance of information architecture & management from OneDrive. Metadata, content types with templates, records management policies. The current state of OneDrive is less powerful than Windows file servers with FCI in 2008, and far less powerful than SharePoint in 2010. Please push that OneDrive team (I'm guessing that's where responsibility lies) to empower OneDrive and thereby Group Files.
Good news! As a part of the new Outlook on the web, the group document library view is the same as the one in the team site.
Susan Roberts commented
With Microsoft group, you could offer an option whether or not as the owner you would like to receive communication in your inbox. Also it seems like my plan does not support sharepoint. That is OK, but it might save time if a popup or a description would proactively tell me that that function is not available on my 365 plan.
PAUL BLAKEBOROUGH commented
We have found some of the elements in Info Management Policy Setting invaluable especially the ability to have the SharePoint Version number pulling as a Label through to print on the document. I am bemused considering all the Document Management requirements of ISO standards that it is so complicated to get a system version number printing in the document
Carsten Isak Nielsen commented
We love groups and all the Group features, but the document management part of it is currently non-existing. I know we can create/script a new ECM document library on the group SharePoint site and add our own content types and metadata to that library as you recommended at Ignite in Atlanta. BUT and here is the catch, “Convenience is king”. The users will NEVER move the files to the ECM library, and if they try, we might end up with multiple versions in different locations (Copy files).
What I hear that our clients really want is, a way to add any library in SharePoint with FULL SharePoint view, Content type and metadata functionality. Perhaps even a way to set the Custom Library as default integration point for the group. This way you can keep the simple document view and library for simplest possible usage scenario, and enable groups to support ECM if we can add our own library’s. You are close in Teams, where we can add multiple libraries, but still it’s not possible to customize the view, content types or metadata.
We have seen the Cards view in Outlook files tab, but as Shania Twain said, “that don't impress me much” when we have lots of files.
It would be REALLY nice if the group administrator could choose an existing SharePoint library to store the group documents. I would avoid spreading information around and help organization to maintain an information architecture. We could then have multiple groups using the same library/sites for different purposes.
Nick Edwards commented
Content types - maybe have the ability to inherit content types from a Sharepoint site... in fact groups sitting under a Sharepoint site would be very useful. But also please add external document sharing.
Evan Riser commented
Couldn't agree more, content types and managed metadata serve as unifying properties in SharePoint and need to be applied to all of office 365. Without the IA constructs we have grown to depend on in SharePoint available across O365 users will have a harder time surfacing content and we will end up with the same information silos that O365 is supposed to eliminate.
The lack of feedback from MS does not bode well. Clients that have thousands of teamsites see this as a maintenance/governance/IA nightmare waiting to happen.
Piotr Prussak commented
Another vote for allowing metadata in group files. That is killing me from building mini-apps in groups.
Per Ove Sandhåland commented
Our customers and us, has great search solutions to make information that is stored in different libraries, webs and site collections findable.
Please make content stored in Groups libraries findable as well.
The users need to easily add metadata.
They should also be able to choose templates.
How you do this is not as important as the result of the features.
But using the effort laid into metadata and the search system, could be an easy way to achieve this.
Tagging documents in Delve AFTER the documents or contents is not a easy way to achive the goal.
Make everything findable.
Sudesh Withanage commented
same settings from SharePoint library is needed for examples enabling minor versions. This is important when it comes to migration of data from SharePoint libries.