CISAC code of the issuing society, year of declaration in IDA database, row number (attributed by the societies set to zero each year) and a control key calculated on the basis of ISO 7064.
shared : A work where more than one society is actively representing rights for, meaning the shares are splitted between several CMOs.
enriched : A work where some fields were populated by a different CMO than the one that initially created the work.
owned :A work is owned by the society that created it in the first place. The 3 first digits of an IDA reference are the society code of that CMO.
List of fields that can be enriched:
keywords, isan, shooting languages, production country, real exploitation, other title, isan title, title of prexisting-work, participant, right owner, reference, link
List of fields that can NOT be enriched:
Every fields excepted the list above, are read-only, except for the CMO that initially created the work in IDA.
Many fields are mandatory at the creation of a work, those are generally not editable by other CMO.
Important notice about an “enriched work” in IDA :
The behavior is different according to the context:
• In the Advanced search, a work is considered “enriched”, regardless of which field was updated.
• In the Dashboard “Work registrations and enrichments” a work is considered “enriched”, if any of the “participant” fields was updated.
In IDA, this is called an “enriched work”, meaning it’s a work where some information where added by a different CMO than the one which initially created the work. It can happen for work related info as well as participant related info.
When the field appears in pink in the information about the work itself, it means that the field was added by a different CMO than the one that initially registered the work.
When the field appears in pink in the information about a participant, it means that the role is administrated (or managed) by a different CMO than the one that initially registered the role.
On one side, you have to consider the authorization applied on the fields. Authorizations on fields depends on who created the work and/or enriched the field. Some fields are reserved to the CMO that created the work.
On the other side, fields can be updated using GUpdate or update ‘Field by field” but the authorizations on fields remain the same, no matter how you choose to update it
“Ownership” of fields can be transfered from one society to another when it’s about the distribution scheme.
Fields about the works itself are generally not reserved (meaning any CMO can update it).
Also, many fields are mandatory, and conditions are depending on the type of works. This can also cause many errors, if you re update includes the deletion of a mandatory field for instance.
Please see our tutorial to know better about updating.
It depends more of the size of the xml import file. It’s recommended not to exceed the size of 100 megabytes (unzipped) for each single file imported. (20 000 – 30 000 works).
Your local database priorily has to comply with IDA standards and rules. IDA membership comes with a special training to assist your organization in deploying the system.
