Page tree
Skip to end of metadata
Go to start of metadata
Introduction to this page

All Chorus metadata behaves in the same way: It cascades down.

All metadata in Chorus will ‘cascade’ down onto the spaces, folders, and files located beneath it in the site’s hierarchy.

This means that a file will inherit metadata from folders and spaces above it. This dramatically reduces the time and effort you need to spend managing metadata.

Why does Chorus work this way? 

Cascading metadata makes it easy to strategically apply metadata to large numbers of files:

  • Apply metadata to a space  in your site’s hierarchy, and you have quickly and efficiently applied that metadata to all the files below that space.
  • Apply metadata to a different space, and you have applied different metadata to all the files below that space.
  • Move a file to a different space, and it will use the metadata panels and values of its new location (but move it back, and the old metadata will reappear).

Cascading metadata means the best of two worlds

  • A file that appears in different spaces can have different metadata in both.
  • As more specific metadata is applied to subspaces and folders within a space, the files in those locations become even more valuable and reusable to the users and teams who work there. Users see the metadata appropriate for their space - in effect, personalizing their view to them.

How is cascading metadata managed? 

  • The metadata of any space is organized and managed in its metadata catalog
  • Like the metadata itself, metadata catalogs also cascade down through the site. All subspaces inherit the metadata catalogs of their parents. 

Good to know: The automatic inheritance of cascading metadata panels can be manually disabled by managers of any space.


You are here:


Metadata cascades down
through the spaces ...

... which means that every space
inherits metadata from its parent.