Do you want to add your repository to the registry?
Contact us! We can talk or send us an email to
REGISTRY SERVICE Requirements Where the resources are located? They need to find material which satisfies their needs Organization and management Defining additional information for content collections. 5
REGISTRY SERVICE Use case. Ariadne Harvester Harvester Harvester Harvester Registry Federated search layer Federated search layer Scalability? 6
REGISTRY SERVICE ArchitectureContent and interfaces 7
REGISTRY SERVICE ArchitectureDifferent functionalities 8
REGISTRY SERVICE Registry data model (1) IMS LODE Registry based on content collection describes: The copyright: author – access rights - … What is the content collection about? Contains other content collections? Where is the content collection located and which protocol implements? 14
A content collection is defined as a group of digital content which is
exposed to the world through some protocols based on standards or specifications. - based on IMS Dublin Core Collections Application Profile specification and complemented with ISO 2146 and IEEE LOM. 15
REGISTRY SERVICE GLOBE approach - There is several ways to create content collections: - Based on the shared metadata information of the learning resources. i.e. subject math - Based on abstract information that a user can defines. i.e. user description like “this is the content collection used by me during all my degree”
This responsibility relies on the content providers because they have
to define their own strategies. Ariadne creates Metadata collections Repository <-> Collection 16
REGISTRY SERVICE Current content 68 repositories 23 SQI targets 1 SRU target 52 OAI-PMH targets 1 SPI target Situation: 7 repositories with SQI+OAI-PMH 1 repository with SQI+OAI-PMH+SPI Repeated: 1 TLÜ repository. It exists in different collections 18
REGISTRY SERVICE Conclusions The ARIADNE registry exposes more than 1 million of LOs Federation of registries Optimized management of tools Interoperability with other networks exposing the collection through standards. 19
REGISTRY SERVICE Future work (1) Integration of the registry in the federated search layer.
Automatic checking of the availability of the SQI targets.