Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
11 results found
-
Sort metadata templates / メタデータテンプレートの並び替え
Metadata templates are arranged in ascending order based on "the template key".
"The template key" often do not match with custom templates written in Japanese, so this specification is inconvenient for users looking for these.We would like the administrator to be able to freely change the display order in the Admin Console.
（IN JAPANESE）
現在メタデータテンプレートは、テンプレートキーに基づいた昇順で並ぶ仕様となっています。
日本語のカスタムテンプレートとそれに紐づくテンプレートキーは、名称が一致しないためユーザーがテンプレートを探す際に不便です。
管理者が自由に表示順を変更できるようにしてください。5 votesAn updated Metadata admin UI has been delivered that allows the Metadata templates to be sorted alphanumerically by their display name, number of fields, or Visible/Hidden status.
-
Add a report that lists metadata set for folders and files.
There are many metadata templates, and each users can set them.
In this situation, being able to see in lists what metadatas are actually applied to which files/folders and what values are set can be very helpful in managing contents and metadata.102 votesThe ability to optionally include Metadata in Folders and Files report has been delivered and is generally available (GA).
-
Move order of Metadata Template Fields
When editing an existing Metadata template, I would like to be able to move or shuffle the order of the fields.
I created an applicant metadata template and need to add in a dropdown for field for "Education Major." Currently the Education fields are towards the top of the template. I would like to be able to insert a field or move the fields to maintain grouping without having to rebuild the whole template.
3 votes -
Metadata Cascading with Overwrite does not update but deletes and creates Metadata Instances
The request here is for box to update the current metadata instance object if already exists on a file/folder instead of deleting and creating new instance when cascading policy with overwrite is applied to a folder.
Box in the current behavior of Metadata Cascading with Overwrite option deletes the
existing metadata Instance and creates a new metadata instance object, this is causing conflicts when any custom business process through API has to manage metadata on items under the cascaded folders. The process gets caught into a scenario where between get metadata and update metadata methods during update the custom process…3 votesCascading Metadata that results in an overwrite now uses a single Update operation rather than Deleting and Creating.
-
Search on metadata multi-select fields
For example, if a customer tags a file with the "Department" key and the values: "Finance" and "HR." "Department" does not appear in the Box UI search bar as a metadata filter option b/c it is multi-select.
79 votesWe have released the ability to search over Metadata multi select fields on the web. Here is a link to the community post: https://support.box.com/hc/en-us/articles/360057067553-Search-Metadata-multi-select-fields. You can also search over such fields using the API: https://developer.box.com/reference/get-search/#param-mdfilters.
Documents uploaded/updated with MD multi select fields from this point going forward will be searchable via that field. Previously uploaded documents with MD multi-select fields will soon be searchable via those fields (backfill is in progress).
-
Add ability to pre-populate some metadata template values
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.
5 votesCustomers can consider using Cascading Folder Level Metadata to pre-populate Metadata values on files & folders.
-
Folder-Level Metadata Exposed in the Webapp UI
Key Components:
--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 -
Maintain Metadata when Copying a File
Currently, Metadata (custom metadata and applied metadata templates/values) that's been added to a file is NOT maintained when a file is copied in Box. This request is to add the functionality - perhaps as an option in the 'Copy' flow - to copy a file's Metadata as well.
32 votesThere is a toggle you can set (via the V2 API) on a template to indicate that you’d like the MD to remain on item copy. See “copyInstanceOnItemCopy” at https://developer.box.com/reference/resources/metadata-template/.
-
Metadata Inheritance (Folder-Level) via Cascade Policies
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 -
Hidden Metadata Templates/Attributes still need to be modifiable and searchable via API
Managed users should not be able to edit metadata that is used by applications. But they still need metadata on those files.
9 votesHidden 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.
-
Templates - Raise Max. Templates per EID to More than 50
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 votesWe have now raised the limit to 500 templates per enterprise.
- Don't see your idea?