Hierarchy of Project, Libraries, and Tags



A Library is the container in which MediaFiles and associated data are stored.


Every MediaFile is in exactly one Library.


In earlier versions we grouped MediaFiles by user. The Library aims to be an abstraction away from user-centric file ownership to facilitate sharing.


The custom MediaFileUserMetaData is stored within the Library. While the MetaData entries are unique to a file, the Fields used to define these values (e.g., “Author”, “Date”) are common to a Library. See [[MediaFileUserMetaData]]


Projects are the primary organizer that users work with. A Project contains links a set of MediaFiles that are tagged or otherwise processed.

Tag Classes

Each Project contains a collection of TagClasses. These classes are common among all of the TagSets in a Project, but are not shared outside of the Project.


See Also TagSet.

A collection of Tags. TagSets can be used to group Tags in many ways. For example:

  • A set for each user that hand tags
  • A set for an automatic tag discovery process (Machine Tags)
  • A set for each category of tag, e.g.,
    • Spoken Words
    • Individual Syllables
    • Background Noise
    • Bird Species


Each Tag is in exactly one TagSet.