Add a feature to enable site level metadata and default values
A challenge to adoption and use of metadata is getting users to fill in values consistently. There are many scenarios that would benefit from being able to define a value for metadata at the site level and have that automatically push down to all documents/items in that site Examples for the type of metadata that could be set centrally are project name, IDs from ERP systems, commercial sensitivity etc - all of those would be good to filter in search refiners. Content types could deal with this, but use of content types has its own limitations which currently require custom configuration.
Ben Robb (Office Servers and Services MVP)
shared this idea
3 comments
-
Jakob Nøtseth
commented
With modern ui, it is getting even harder to do proper "site" tagging and classification. For example having a project site classified as "project" and tag with the project number. Normally I would have made a single item list on the site and use search for rollup, but since search and ct-hub is so underperforming in modern ui, this should again be considered moved to property bag values. Having some visual way of managing property bag values and be able to reuse property bag values across the site as default column values etc. would really help when using modern ui. Ofcourse search will need to be able to index and query these as well.
-
Mike Hatheway
commented
The defaulting of values request here is a great bonus.
I simply want there to be metadata on site objects in general. There is technically the Title and Description now, just roll that into a Content Type and apply it to all sites. Then allow Owners to inherit from the "Site" content Type and create child CTs like "Project Site", with additional site columns. Then we could switch to that Content Type and really improve the ability to search for "site types".
Similarly it would be great to have Metadata on List and libraries... The objects themselves, not the items in them. -
Marc D Anderson commented
This is something I often add so-called "arbitrary JavaScript via injection" to do in existing list forms. If it were a built-in capability, that would be another reason for script in list forms to be off the table.
