How EIDR Works

The Registry receives and processes registration requests from registrants. Users and applications can look-up and search the Registry. Registrants and lookup users can use the web user interface or web services API to interact with the Registry.

spacer

Registrants Submit Assets to the Registry

A registrant submits objects for registration along with core metadata and information such as the type of object and relationship to other objects. The registrant could be a content owner, an aggregator, post-production house or any other entity authorized to register objects. The Registry requires minimal metadata required to guarantee uniqueness for the full range of asset types.

Registry Assigns EIDR After Verifying Uniqueness

EIDR uses a sophisticated deduplication system to ensure that the object submitted to the Registry has not already been registered while allowing the registration of similar and related objects. The centralized registry structure guarantees the uniqueness of objects being registered. If no duplicate object exists, the Registry generates an EIDR for the object and stores the new EIDR and the corresponding metadata in the Registry.

EIDR for an object consists of a standard registry pre-fix, the unique suffix for each asset and a check digit.

spacer

EIDR is purely functional without any implication of ownership, making it persistent enough to remain the same despite any change in control or ownership of the underlying asset.

Users can search the Registry

The Registry provides both a web-based UI and web-services APIs to enable a user or application to search the Registry using various search criteria. Developers can use the APIs to integrate the Registry features with their applications and automated workflows.

More Technical Information

To find out more about how EIDR works, please visit the Resources section. Additional technical documentation can be found on this page along with general, business, FAQ’s information.

spacer

 
 
gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.