The Apple Feed delivery workflow supports both 3.5 and 3.6 deliveries (and generally, any versions) as the entire validation mechanism is dynamic, based on the .xsd
files associated to the metadata templates used.
However, we do not recommended attempting deliveries for multiple versions on the same organization as there is only 1 master Catalog file and 1 master Avails file that is in use per platform.
An Apple feed delivery can be triggered at any time from:
When triggering the Apple Feed delivery workflow, a custom 3-step wizard process is displayed. This process is meant to facilitate adding titles, reviewing and fixing errors, and ultimately delivering the Apple Catalog (and, if needed, the Apple Avails as well):
In step 1, the Apple Feed delivery workflow validates the selected metadata templates.
There are multiple layers of validation in place that are applied for both the Apple Avails metadata template and the Apple Catalog metadata template:
contentType
values configured, as per the definitions found in the associated .xsd
file of the metadata template. contentType
configured multiple times. .xsd
file of the metadata template. With the exception of validating that the metadata templates have the <umcAvailability> or <umcCatalog> tags, all the validations are dynamic.
An Apple metadata template should contain the appropriate .xsd
file (either for Avails or Catalog) which will be used to validate the metadata template itself in Step 1.
What is a required value, what are the correct contentTypes, these validations are derived from the .xsd
file.
To correctly validate and deliver an Apple Catalog for version 3.5, make sure to use the 3.5 .xsd
file when saving the metadata template.
.xsd
file associated with the metadata template. There are no hardcoded validations in place. .xml
files with the information. Additionally, artworks may also be delivered if they are part of the delivery. .xml
files to the configured platform locations. Each organization can only have 1 Apple Feed delivery workflow at one time. Starting a new one when the existing workflow has not finished will overwrite the previous delivery.
At the end of each Apple feed delivery workflow, there can be two separate change logs that are generated: one for Apple Catalog and one for Apple Avails (if an Avails metadata template was used).
The same process is used for creating a first version of the Apple Catalog and Apple Avails, and also for updating existing versions of them.
If the titles already present in the Catalog or Avails have modified values, when a new version is created, the change logs displays all the modifications.
To perform an Apple feed delivery:
Configure your selection of titles.
Source files are not mandatory to be present in titles for Apple Catalog or Apple Avails deliveries, with the exception of specific artworks.
Configure a metadata template for Apple Catalog. Use the correct .xsd
file for the Catalog version you are trying to deliver, for example, 3.5 .xsd
or 3.6 .xsd
.
Configure a metadata template for Apple Avails. Use the correct .xsd
file for the Avails version you are trying to deliver, for example, 3.5 .xsd
or 3.6 .xsd
.
Configure a platform with all the necessary information. For more information about Apple platforms, see Configuring an Apple platform.
Optional: Assign iTunes type package templates to the platform.
When trying to deliver iTunes packages, make sure you add a naming convention in the organization settings that will enforce the .itmsp
extension on the package.
Trigger an Apple feed delivery workflow from the Connect header.
Afterwards, the workflow can also be triggered from individual titles or from the bulk action menu, inside the Apple Catalog page.
In Step 1 - Titles, of the Apple feed delivery workflow:
Proceed to the next step. In Step 2 - Metadata, of the Apple feed delivery workflow:
.xml
file to confirm that your titles have been added to the catalog. Whenever you trigger and complete an Apple Feed Delivery workflow, Connect rebuilds the entire Apple Catalog and automatically updates all of the existing titles inside of it. This means that regardless of your title selection, all metadata changes on all the Catalog titles are included automatically in any new version of the Apple Catalog.