In order for sub-organizations to submit a release to a super organization, they are required to provide certain metadata.
The Sub account metadata submission feature in FUGA Next will allow you to tailor the metadata requirements for your sub-organizations’ submissions.
The feature allows you to define the metadata requirements for all sub-organizations, enabling you to enforce stricter requirements or allow sub-organizations to only supply basic metadata.
The feature can be found by navigating to System Settings, and selecting ‘My Organization’.
In the Sub account settings you can select the following two options:
Option 1: Require Basic Metadata (default)
This option requires the sub-organization to provide basic product information for their submissions, such as titles, artist information and audio files. This option will likely require you to provide additional metadata after accepting the submission, before it can be delivered to DSPs.
Option 2: Require Detailed Metadata
This option requires the sub-organization to supply detailed metadata that makes the product ‘ready for distribution’ upon submission to your organization.
This means that the sub account will need to provide a UPC for the product and ISRCs for all tracks, as well as all other metadata required before you can ‘approve’ the product in your FUGA Next account.
Until all metadata requirements have been met, the sub-organizations will see the ‘Missing fields’ message on the product page and cannot submit their release.
Please note that the detailed metadata requirements are determined based on your active DSP connections, and will align metadata requirements between your account and your sub-organizations.
For example: if you are required to provide composer and lyricist information, your sub-organizations will need to provide this information as well in order to submit their releases.
After accepting the product from the sub-organization, it is still possible to make changes and add more information.
Please note that with either option, the setting is applied to all the sub-organizations under your account as a blanket option. You can not apply the setting to select sub-organizations.
Review process
In addition to enforcing stricter metadata requirements on your sub-organizations, you will also have a more detailed overview of submitted products and their metadata before accepting/rejecting submitted products.
Submitted products overview
The submitted products overview indicates whether a product adheres to the configured metadata requirements by marking it as ‘Ready’ or ‘Incomplete’.
Submitted product detail view
You can then open up the product detail view in order to see which information is missing, and would need to be entered by the main org were you to accept the submission in its current state.
FAQ
What information is required in ‘Basic’ mode?
On product level
- c_line_text
- c_line_year
- label
- language
- genre
- name
- p_line_text
- p_line_year
- release_format_type
- has at least one asset
- primary artist
- cover image
- all assets have the required fields
On asset level:
- genre
- name
- file
- primary artist
What metadata is a sub-org required to supply in ‘Detailed’ mode?
This is dependent on your current DSP connections.
For example, if you deliver to Spotify via FUGA Aggregation, you will be required to provide Composer & Lyricist information. If you enable ‘Detailed’ mode for a sub-org, they will also be required to provide this.
The following additional information may be required depending on the DSP connections:
- Composer/Lyricist information
- Original release dates
- Audio language information
- Localized metadata (Space Shower only)
Can the submission mode be changed?
Yes, the setting can be changed at any time.
What if sub orgs can’t provide barcodes and ISRCs?
Please reach out to FUGA Support (support@fuga.com) and we may be able to enable a feature for a sub-org to automatically generate barcodes and ISRCs.
Can I exclude certain sub accounts from this setting?
No, this is not possible. The setting used will be applied to all sub-accounts.
Can I exclude certain fields from the requirements?
No, this is not possible.