Forum Discussion
New Library UI - non-required "Required" metadata
Anyone have ideas on how to promote this topic and get someone at Microsoft to provide some guidance. My organization really needs to know if this type of enterprise functionality is even part of the future SharePoint. Or do we need avoid content types and required metadata in our design/migrations? I see no comments about this elsewhere, or any mention in the roadmap. Maybe 3rd part workflow/forms tools will need to supplement (would need to think this through and experiment). Maybe it is a matter of a new way of thinking as pointed out by Andrew Gilleran, but there are business processes that will need to be rebuilt.
MicrosoftHey all! Sorry we've been busy getting ready for the SharePoint Virtual Summit (join us! https://aka.ms/SharePointSummit) on May 16th.
The good news is that we TOTALLY UNDERSTAND the situation and the challenges you're describing, as well as the challenges many customers faced with the 'classic' model that prevented documents from being visible to team members if required metadata was not completed. There is work being done to address the scenario. We're not ready to announce the details, yet.
I'll add LincolnDeMaris and Chris McNulty to this and will let them reply when they have a chance.
danholme wrote:Hey all! Sorry we've been busy getting ready for the SharePoint Virtual Summit (join us! https://aka.ms/SharePointSummit) on May 16th.
The good news is that we TOTALLY UNDERSTAND the situation and the challenges you're describing, as well as the challenges many customers faced with the 'classic' model that prevented documents from being visible to team members if required metadata was not completed. There is work being done to address the scenario. We're not ready to announce the details, yet.
I'll add LincolnDeMaris and Chris McNulty to this and will let them reply when they have a chance.
Hey danholme, now that the Virtual Summit is over, may we expect some traction on this front? the modern experience is turning out not-so-modern for our users. Lots of frustations and friction in switching from classic to modern. Too many rough edges.
LincolnDeMaris and Chris McNulty any updates on this?
Hello all,
I think there is some good news. Last week I was at the Ignite. A lot of news. Fot example there will be a new view in a library that show you files with incomplete metadata.
But there was more. During a Demo they showed that when you upload a couple of documents to a New library with required metatdata you get a prompt that there is a problem.
This video starts at the moment where this is being explained.
https://www.youtube.com/watch?v=awDKyeRgslc&feature=youtu.be&t=1340s
It starts at 22.20
This is excellent. It appears to answer our questions about how to manage required metadata. Certainly hope it is released soon to test. I did not have a chance to go to Ignite, so thank you for posting the vid.
- Thanks @Dan. Yes, we've been working on the required-but-not-required metadata situation for a while, and we've designed a solution that we're not ready to show just yet, but it IS coming. Having written the book on MD (literally), I care a lot about this, too.
I have an issue with the way the metadata works in Sharepoint when document check-in/check-out is being used to manage document versions.
Generally, the purpose of using check-in/check-out is to manage the version of a document for traceability and other reasons. The only time the version of the document should change is when the content of the document changes and this include changes to some types of metadata.
However, there is 2 types of metadata associated with a document:
- The metadata that is part of the document content. If this changes so does the version of the document. For example: Title, Author, Publish date.
- Metadata that is used for classification (taxonomy) of the document for storage or searching purposes. In this case the metadata can be changed without changing the content or version of the document. For example: If a (physical) book is out in a (physical) library it might be listed under several subjects.
The problem in Sharepoint is that if check-in/check-out is required there is no way (as far as I know) to change metadata associated with the document without raising the version number.
Sharepoint needs some mechanism that allows classification (taxonomy) metadata to be updated without changing the version number.
If this could be done, then the taxonomy provided by the term store would become a very powerful feature.
Thanks Chris McNulty - The emphasis is often on on the most recently released stuff so those of us that want to leverage MMS and Content Types and Site Columns and Search, are not always sure if MSFT is committed to these techologies (supporting and improving). Yes - you did write a book on the subject and I still have the copy I got at the Puget Sound SharePoint User Group years ago. :-) - Greg
Excellent! Thank you Chris and Dan for the update. We look forward to more information, and hopefully seeing it on the roadmap asap. Maybe we'll hear about it at the May virtual summit? *wink *wink*
