Your SlideShare is downloading. ×

Registry slides for Se@m Workshop

879
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
879
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. REGISTRY SERVICE
    Standardizing the organization of our content collections
    harvesting – OAI -PMH
    federation
    Content collection
    metadata discovery
    publishing– SPI
    standardization
    collections – IMS LODE
    Cruise Control
    2
  • 2. REGISTRY SERVICE
    Overview
    • Small registry demo.
    • 3. Additional information about our work.
    • 4. Requirements.
    • 5. Why do we need the registry? Ariadneuse case
    • 6. Architecture. Functionalities of the registry.
    • 7. Synchronization of registries
    • 8. Real functionality of the federation. Federated Search and Harvest.
    • 9. Other approaches
    • 10. Current context
    • 11. Conclusions
    • 12. Future work
    3
  • 13. REGISTRY SERVICE
    Additional information
    - JorisKlerkx will present the general GLOBE architecture overview on
    Thursday at 12:00 ECTEL 2010 (Audit 1).
    • Currently, it is used in:
    • 14. ASPECT project - http://www.aspect-project.org/
    • 15. ICOPER project - http://www.icoper.org/
    • 16. GLOBE consortium - http://www.globe-info.org
    • 17. Share.TEC project (soon) - http://www.share-tec.eu/
    • 18. Do you want to add your repository to the registry?
    • 19. Contact us! We can talk or send us an email to
    ariadne@cs.kuleuven.be
    4
  • 20. 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
  • 21. REGISTRY SERVICE
    Use case. Ariadne
    Harvester
    Harvester
    Harvester
    Harvester
    Registry
    Federated search layer
    Federated search layer
    Scalability?
    6
  • 22. REGISTRY SERVICE
    ArchitectureContent and interfaces
    7
  • 23. REGISTRY SERVICE
    ArchitectureDifferent functionalities
    8
  • 24. 9
  • 25. REGISTRY SERVICE
    10
  • 26. 11
  • 27. REGISTRY SERVICE
    12
  • 28. REGISTRY SERVICE
    13
  • 29. 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
  • 30. REGISTRY SERVICE
    Registry data model (2)
    • 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
  • 31. 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
  • 32. REGISTRY SERVICE
    Other approaches
    17
  • 33. 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
  • 34. 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
  • 35. REGISTRY SERVICE
    Future work (1)
    Integration of the registry in the federated search layer.
    • Automatic checking of the availability of the SQI targets.
    • 36. Access rights and user management?
    • 37. Proposing improves on the different specifications.
    • 38. How to deal with the repeated instances?
    20
  • 39. REGISTRY SERVICE
    Questions?
    21