Content Explorer - metadata view v1

​

Prerequisites

• Read the guide.
• Check the .
• Check the information on .

​

Create and configure an app

1. .
2. Add the local development address in the CORS Domains:
3. Generate a .

​

Create a metadata template

1. Use or Admin Console to create the template.
2. Apply an already created template to a Box folder. Make sure you enable the cascade policy. For detailed instructions, see instructions on customizing and applying templates.

​

Display name and key parameters

• The displayName parameter is the display name of the template visible in the Admin Console.
• The templateKey parameter is a unique identifier of the template. It needs to be unique across the enterprise for which you create the metadata template. If you don’t provide the templateKey parameter, API creates a unique one based on the value in displayName.
• The [fields].displayName parameter is the display name of the field as it is shown to the user in the web and mobile apps.
• The [fields].key parameter is a unique identifier for a specific field in the template. The identifier must be unique within the template to which it belongs.

​

Display metadata view

1. Clone the metadata sample project.
2. Update the placeholders in App.js with actual values:

   Parameter	Description
   DEVELOPER_TOKEN	generated in the the Developer Console.
   ENTERPRISE_ID	Enterprise ID copied from the General Settings tab of your Box application.
   METADATA_TEMPLATE_NAME	templateKey of your already created metadata template. Note: To make sure you provided the proper name, use the to retrieve the name, or copy it from the URL in the Admin Console. If you decide to change the template name in the UI, you change the display name only. The name to use in the component is always the one you provided at the beginning.
   METADATA_SOURCE	Source of your . It’s a string that combines the scope, enterprise ID, and metadata key.
   ROOTFOLDER_ID	ID of a Box folder to which you want to apply the metadata query and display filtered files.

   The defaultView, fieldsToShow, and metadataQuery parameters are already defined in the sample project. Examples of these parameters are available in the sample project.

   Parameter	Description
   defaultView	A required prop to paint the metadata view. If it’s not provided, you get the regular file view.
   fieldsToShow	Add or hide specific metadata columns to display in the Content Explorer.
   metadataQuery	Provides a way to find files and folders by searching for the metadata attached to them. For additional information on metadata queries, see .

3. Pass the required parameters to the Content Explorer component.

function App() {
    const token = "<DEVELOPER_TOKEN>";
    const rootFolderID = "<ROOTFOLDER_ID>";
    const EID = "<ENTERPRISE_ID>";
    const templateName = "<METADATA_TEMPLATE_NAME>";
    const metadataSource = `enterprise_${EID}.${templateName}`;
    const metadataSourceFieldName = `metadata.${metadataSource}`;
    const metadataQuery = {
    	from: metadataSource,
    	query: "key = :arg1",
    	query_params: { arg1: "value" },
    	ancestor_folder_id: 0,
    	fields: [
        `${metadataSourceFieldName}.name`,
        `${metadataSourceFieldName}.last_contacted_at`,
        `${metadataSourceFieldName}.industry`,
        `${metadataSourceFieldName}.role`,
        ],
    };

    const fieldsToShow = [
    // canEdit propetry determines if the user can edit the metadata directly from Content Explorer component
    { key: `${metadataSourceFieldName}.name`, canEdit: false },
    // displayName alows to change the label on metadata column
    { key: `${metadataSourceFieldName}.industry`, canEdit: false, displayName: "alias" },
    { key: `${metadataSourceFieldName}.last_contacted_at`, canEdit: true },
    { key: `${metadataSourceFieldName}.role`, canEdit: true },
    ];

const defaultView = "metadata";
return (
    <IntlProvider locale="en">
        <div className="App">
            <header className="App-header">
                <h2>Metadata view in Content Explorer</h2>
            </header>
            <section>
                <div className="metadata-based-view">
                    <ContentExplorer
                        rootFolderId={rootFolderID}
                        token={token}
                        metadataQuery={metadataQuery}
                        fieldsToShow={fieldsToShow}
                        defaultView={defaultView}
                    />
                </div>
            </section>
        </div>
    </IntlProvider>
);
}

export default App;

​

Metadata keys

​

Metadata keys sanitization

• No hyphens - or underscores _ are permitted.
• Only letters (a-z, A-Z) and numbers (0-9) are allowed.

• field for the first occurrence
• field1, field2, and so on for subsequent occurrences