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.
133 results found
-
Increase Metadata query scale limits
Increase the character, results, and other scale limits for metadata and metadata query search APIs. The documentation indicates additional volumes of data and is inconsistent. In order to provide solutions similar to legacy ECM, metadata query should be able to return additional results sets.
2 votes -
Metadata overlay as header / footer or document watermark
Legacy ECM technology can overlay metadata attributes directly on versions of the document or when the document is printed. Metadata overlays are used for audit trails, SOPs, and other "point-in-time" compliance & records management use cases. In order to provide capabilities on par with legacy ECM technology, Box should consider additional advanced metadata features, such as printing or watermarking certain file types with attributes.
5 votes -
Updating metadata date to current date button
Having a button that would "Use Current Date" Would be a great benefit. Updating any date that is older than 10 years old takes two clicks. We have two dates associated with documents, being able to have a button that says use current date would save a lot of time when documents are updated.
1 vote -
Regarding the display format of metadata reports
Is it not possible to set the output format arbitrarily when generating reports from metadata, rather than being limited to JSON format?
I would also like to have commas inserted into numeric fields of metadata to format them with thousands separators.(in Japanese)
【メタデータレポートの表示形式について】メタデータでレポートを出力した際に、JSON形式ではなく表示形式を任意に設定できないのか。
また、メタデータの数値フィールドの桁数にカンマを入れてほしい。2 votes -
Add information in “File Properties” to metadata
Currently the information in the “File Properties” (owner, created date, retention policy exp, size) is all siloed and unusable for anything but viewing in preview. Adding that information as normal Box metadata will make it available for reporting, sorting, as a policy trigger, and consumable by Crooze for tasks like retention policy expiry reports.
4 votes -
When creating a metadata template, allow the user to select the target folder, so that the metadata is used only under a specific folder.
Currently, when a metadata template is created, it is published within the tenant.
Thus, all metadata is desplayed , make it difficult use when setting metadata. Also, there is a possibility that metadata will be setting to content that shloud not be.So, when creating a metadata template, we would like to make metadata template only be used under a specific folder by allowing the user to select the folder to be used.
(in Japanese)
【メタデータテンプレートを設定する時、フォルダを指定し、そのフォルダ配下でのみで使用したい】現在メタデータテンプレートを作成すると全体に公開されてしまうため、必要なコンテンツ以外にメタデータテンプレートが付与されてしまう可能性があります。
また、たくさんのテンプレートが見えると非常に使いにくいです。メタデータテンプレートの設定をする時、ユーザーが利用できるフォルダを指定し、特定のフォルダ配下のみで利用できるようにしてほしいです。
25 votes -
I have some files sorted into collections. It would be great if I could select all the files and tag them.
Currently you have to tag each file in a collection individually. If you select all the tag option disappears.
1 vote -
Option to overwrite metadata values when moving file
We would like the option for a metadata attribute to be overwritten automatically when moved to a folder with cascading metadata enabled for the same metadata template.
Here's our use case:
Some of our organization content currently sits in user folders. People accessing that content have no way of knowing where it sits, and therefore can't take action to move it to the desired location. Applying a metadata template indicating if content sits within a user or an organizational folder would be a great way to make this visible to users. With the current behavior, we can't do that, as…2 votes -
Request to improve metadata_query limitation
Metadata queries Limitations
https://developer.box.com/guides/metadata/queries/limitations/When sending a metadata query request for which the result set exceeds 2,000 items, the API can only guarantee that it returns all all matching results if both the following conditions are met.
1.The requesting user has at least Previewer permission to all items in the result set
2.The ancestor folder contains all of the files in the result setWith the above limitation, it is not possible to narrow down the search to metadata for a specific folder when the range of metadata assigned is wide.
Could it be improved so that the number of…2 votes -
Custom document repositories with metadata search
User groups often look to create an interface for document repositories for content stored on Box, where metadata could be used to search/filter content. That would be an interface with medatada fields similar to what can be found on websites (i.e. https://www.calpnetwork.org/library/). The current experience of using the native search, then selecting a single metadata template, then selecting an attribute is not sufficiently user friendly and it's not possible to embed a pre-selected set of metadata fields for search onto an intranet or website.
We're currently not using metadata templates much, but this would be a very practical way…1 vote -
create folder based on metadata
Request: Give users the ability to create a folder that pulls in all files with specific metadata values
1 vote -
metadata template.Data type: Amount,partial search
I have two requests.
I would like to add "Data type: Amount" to the metadata template.
I would like to be able to search metadata templates using partial search.
1 vote -
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 votes -
If we make changes to the metadata template, the changes should be reflected in the metadata of the created file request link.
If we make changes to the metadata template, the changes should be reflected in the metadata of the created file request link.
When changing the item name of a metadata template or the display order of text item choices,The changes are not reflected in the configured file request screen.
When the number of file request settings is large, the metadata templates need to be changed manually one by one when there is a change in the metadata template. This is a burden on workers and leads to a decrease in operational efficiency.メタデータテンプレートに変更を加えた際に作成済みのファイルリクエストリンク内のメタデータにも変更を反映して欲しい
メタデータテンプレートの項目名変更や、テキスト項目の選択肢の表示順を変更した際、設定済のファイルリクエストの画面に変更内容が反映されません。
ファイルリクエストの設定件数が多い場合、メタデータテンプレートに変更があった際に1つずつ手動で変更が必要なため作業者の負担となり業務効率の低下に繋がります。8 votes -
HASANY/HASALL implementation of metadata queries / メタデータクエリのHASANY/HASALLの実装
I would like to implement HASANY/HASALL for metadata queries.
We have implemented it in the released functionality with reference to the Metadata Query Toolkit, but suddenly it is no longer available and we are having trouble. The answer was that there is no alternative.https://cloud.app.box.com/s/zbit25jyv5xxv0649nngz0rckofjludx#p=9
(IN JAPANESE)
メタデータクエリのHASANY/HASALLの実装を希望します。
Metadata Query Toolkitを参考に、リリース済みの機能に実装しておりましたが突然使えなくなり困っております。また代替え案もないとの回答でした。https://cloud.app.box.com/s/zbit25jyv5xxv0649nngz0rckofjludx#p=9
5 votes -
Apply Classification labels on multiple items
It's not currently possible to select multiple files or folders and classify them all at once. We have to click the More Options button on each item to apply the labels one-by-one. I need to apply classifications to about 40-50 existing folders so I'll have to do them individually. Please consider allowing us to click the checkboxes next to multiple items and then show the classify option under More Options, or add a button alongside there next to the Move/Copy, Collections, Trash buttons, etc.
Update: I discovered that you can use a Box Relay workflow using a Manual Start trigger…
2 votes -
Metadata template creation - option to duplicate metadata template, then edit
A lot of the metadata templates will have similar fields, so ideally you could duplicate an existing metadata template, then make edits from there rather than just having the option to start new each time.
3 votes -
Metadata in reports
I would greatly appreciate it if you could assist me in creating a report for the documents within the folder. My goal is to see all the metadata associated with each of the files uploaded to that particular folder. Your help in this matter would be truly valuable.
4 votes -
Metadata Instance Update - Remove when no value should not fail
When Updating a metadata instance to remove a value from a specific instance, currently today the API fails if the field has no value.
I would like to propose that if the field had a value it is removed, and if it doesn't - then just ignore the operation. Similar to what add does if the field already has a value, it just silently replaces it.
As an option, in case others are relying on the failure, maybe add a new operation "forceRemove" so that if there is no value, the code will just ignore it and continue with the…
1 vote -
Metadata additonal column
Adding metadata as an additional column into Box interface which is similar to Tags can help to check the status.
The User activity report should have option to pull the report for who add/edit status in the report and should have what the collaborators tried to add.
The user activity report should have ability to get the Tags Add/Edit from the report.
4 votes
- Don't see your idea?