Messages, emails and actions

Browse Bar (version 9.0+)

ResourceSpace utilises the power of metadata to enable users to locate required assets. Whilst this enables flexible and powerful searching many users, especially those new to ResourceSpace have requested the ability to browse the system in a simple and accessible fashion.

Featured Collections are often used to facilitate browsing using a pseudo folder structure, however this requires manual curation to ensure new resources appear.

The browse bar provides a folder-like structure based on metadata, allowing you to freely browse the asset repository in an intuitive and recognisable manner.

The browse bar appears as a side tab and is available on all pages. Clicking this tab will cause a panel to slide out that contains various folders, allowing the resources to be browsed in a number of ways.

Browse by tag

'Browse by tag' allows you to drill down through resource type, metadata fields (fixed list fields only) and metadata field options (nodes). Clicking on a resource type or field option will perform a search for all resources of the relevant resource type with the field option set.

If you have sufficient access you can also create new resource types, metadata fields and field options

* Please note that only fixed-option metadata fields that have been configured to do so will appear.

Featured Collections

This displays all Featured Collection Categories and Featured Collections in a structured tree format. If you have sufficient access you can also create new Featured Collections here

My Collections

This enables quick access to all your collections

Workflow

The workflow folder lists all workflow states (e.g. pending Review, active, archived) that you have access to. Clicking a workflow state will show all resources in that state

Drag and drop

If you have access you can also drag resources from search results page (in thumbnail view only) to items on the browse bar to quickly add metadata to resources.

Resources must be of the same resource type and must not have conflicting metadata already set. This is to prevent conflicts e.g. by dropping a resource onto an option for a 'radio button' type field when the resource already has a value set