Getting data into MusiMap
How your music, metadata, and catalogue information reach MusiMap.
This page answers a practical onboarding question: what do you actually need to give MusiMap, and how does it get there? The answer is organised around your existing situation, not MusiMap's internal architecture.
For where MusiMap fits in your overall platform, start with How MusiMap integrates.
Use your existing storage
Amazon S3
If your audio is already stored in Amazon S3, it can remain in your bucket. MusiMap can be given controlled cross-account access so the services can read the required objects without you redesigning your storage workflow. For AWS customers, this is typically done through controlled cross-account access (AWS AssumeRole), configured with MusiMap during onboarding.
SFTP
SFTP is a supported integration option for customers who use managed file transfer as part of their existing delivery workflow. Audio and delivery files can be deposited through SFTP for ingestion and processing.
Use MusiMap-managed storage
MusiMap can provide managed storage to which you send audio and/or delivery files. This supports:
- manual or application-driven delivery;
- ingestion initiated on request;
- scheduled ingestion;
- recurring or automated catalogue synchronisation.
See the Storage and Ingestions guides for implementation detail.
What you can supply
Audio
MusiMap can process supplied audio files as part of audio-derived intelligence workflows such as MusiTag, fingerprinting for MusiTrace, and catalogue preparation for search and profiling.
Catalogue and metadata
Catalogue information and metadata can be supplied through workflows such as:
- CSV catalogue manifests;
- JSON through the API;
- DDEX deliveries.
Identifiers such as ISRC, your own internal IDs, and other catalogue metadata help MusiMap reconcile your catalogue with processing and returned results.
Audio and metadata are distinct inputs. They can be supplied together or through separate parts of the workflow, depending on the integration. Not every workflow requires every input type.
Ingestion timing
Customers operate in several patterns, and these are not mutually exclusive:
- Batch catalogue delivery for large or periodic updates.
- Recurring or scheduled ingestion for synchronised catalogues.
- Continuous arrival of new content into storage or SFTP.
- On-demand individual-track processing through the API for exceptional or time-sensitive tracks.
A customer may use bulk catalogue ingestion as the normal path and on-demand MusiTag for a time-sensitive release that must be analysed before it enters the standard delivery flow.
Continue reading
How MusiMap integrates
Product models, catalogue sources, and integration choices.
Getting results back
How intelligence returns to your platform after processing.