We'd like the ability to pre-populate some metadata template values. This way, users aren’t constantly re-typing (or constantly choosing from a drop-down menu) the same responses to attributes when applying metadata to a large number of files.4 votes
Customers can consider using Cascading Folder Level Metadata to pre-populate Metadata values on files & folders.
--Allow users to enter Metadata at the folder-level (currently can only add metadata to individual files in the UI)
--Provide a visual indicator (somewhere) on the page to inform users that a folder has metadata33 votes
Allow metadata fields to be applied at the folder level, with files in that folder (or added to that folder) automatically inheriting the metadata fields AND potentially the values associated with those fields.31 votes
Managed users should not be able to edit metadata that is used by applications. But they still need metadata on those files.9 votes
Hidden metadata templates and attributes are modifiable via API. Hidden metadata attributes are searchable via API — hidden metadata templates are not currently. This is on our longer-term roadmap to fix since this is a bug.
EIDs are currently limited to a max of 50 Metadata Templates. This request is to significantly raise the limit of the total number of Metadata Templates per EID.4 votes
We have now raised the limit to 500 templates per enterprise.
- Don't see your idea?