REGISTRY SERVICE<br />Standardizing the organization of our content collections<br />harvesting – OAI -PMH<br />federation...
REGISTRY SERVICE<br />Overview<br /><ul><li> Small registry demo.
 Additional information about our work.
 Requirements.
Why do we need the registry? Ariadneuse case
 Architecture. Functionalities of the registry.
 Synchronization of registries
 Real functionality of the federation. Federated Search and Harvest.
 Other approaches
 Current context
 Conclusions
 Future work</li></ul>3<br />
REGISTRY SERVICE<br />Additional information<br />- JorisKlerkx will present the general GLOBE architecture overview on <b...
 ASPECT project - http://www.aspect-project.org/
 ICOPER project - http://www.icoper.org/
 GLOBE consortium - http://www.globe-info.org
Share.TEC project (soon) - http://www.share-tec.eu/
 Do you want to add your repository to the registry?
 Contact us! We can talk or send us an email to </li></ul>ariadne@cs.kuleuven.be<br />4<br />
REGISTRY SERVICE<br />Requirements<br />Where the resources are located?<br />They need to find material which satisfies t...
Upcoming SlideShare
Loading in …5
×

Registry slides for Se@m Workshop

1,089 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
1,089
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Registry slides for Se@m Workshop

  1. 1. REGISTRY SERVICE<br />Standardizing the organization of our content collections<br />harvesting – OAI -PMH<br />federation<br />Content collection<br />metadata discovery<br />publishing– SPI<br />standardization<br />collections – IMS LODE<br />Cruise Control<br />2<br />
  2. 2. REGISTRY SERVICE<br />Overview<br /><ul><li> Small registry demo.
  3. 3. Additional information about our work.
  4. 4. Requirements.
  5. 5. Why do we need the registry? Ariadneuse case
  6. 6. Architecture. Functionalities of the registry.
  7. 7. Synchronization of registries
  8. 8. Real functionality of the federation. Federated Search and Harvest.
  9. 9. Other approaches
  10. 10. Current context
  11. 11. Conclusions
  12. 12. Future work</li></ul>3<br />
  13. 13. REGISTRY SERVICE<br />Additional information<br />- JorisKlerkx will present the general GLOBE architecture overview on <br />Thursday at 12:00 ECTEL 2010 (Audit 1).<br /><ul><li>Currently, it is used in:
  14. 14. ASPECT project - http://www.aspect-project.org/
  15. 15. ICOPER project - http://www.icoper.org/
  16. 16. GLOBE consortium - http://www.globe-info.org
  17. 17. Share.TEC project (soon) - http://www.share-tec.eu/
  18. 18. Do you want to add your repository to the registry?
  19. 19. Contact us! We can talk or send us an email to </li></ul>ariadne@cs.kuleuven.be<br />4<br />
  20. 20. REGISTRY SERVICE<br />Requirements<br />Where the resources are located?<br />They need to find material which satisfies their needs<br />Organization and management<br />Defining additional information for content collections. <br />5<br />
  21. 21. REGISTRY SERVICE<br />Use case. Ariadne<br />Harvester<br />Harvester<br />Harvester<br />Harvester<br />Registry<br />Federated search layer<br />Federated search layer<br />Scalability?<br />6<br />
  22. 22. REGISTRY SERVICE<br />ArchitectureContent and interfaces<br />7<br />
  23. 23. REGISTRY SERVICE<br />ArchitectureDifferent functionalities<br />8<br />
  24. 24. 9<br />
  25. 25. REGISTRY SERVICE<br />10<br />
  26. 26. 11<br />
  27. 27. REGISTRY SERVICE<br />12<br />
  28. 28. REGISTRY SERVICE<br />13<br />
  29. 29. REGISTRY SERVICE<br />Registry data model (1)<br />IMS LODE Registry based on content collection describes:<br />The copyright: author – access rights - …<br />What is the content collection about?<br />Contains other content collections?<br />Where is the content collection <br />located and which protocol <br />implements?<br />14<br />
  30. 30. REGISTRY SERVICE<br />Registry data model (2)<br /><ul><li> A content collection is defined as a group of digital content which is </li></ul> exposed to the world through some protocols based on standards or <br /> specifications.<br />- based on IMS Dublin Core Collections Application Profile specification <br />and complemented with ISO 2146 and IEEE LOM.<br />15<br />
  31. 31. REGISTRY SERVICE<br />GLOBE approach<br />- There is several ways to create content collections:<br /> - Based on the shared metadata information of the learning <br /> resources.<br /> i.e. subject math<br /> - Based on abstract information that a user can defines. <br /> i.e. user description like “this is the content collection used<br /> by me during all my degree”<br /><ul><li>This responsibility relies on the content providers because they have </li></ul> to define their own strategies.<br />Ariadne creates Metadata collections<br />Repository <-> Collection<br />16<br />
  32. 32. REGISTRY SERVICE<br />Other approaches<br />17<br />
  33. 33. REGISTRY SERVICE<br />Current content<br />68 repositories<br />23 SQI targets<br />1 SRU target<br />52 OAI-PMH targets<br />1 SPI target<br />Situation:<br />7 repositories with SQI+OAI-PMH<br />1 repository with SQI+OAI-PMH+SPI<br />Repeated:<br />1 TLÜ repository. It exists in different collections<br />18<br />
  34. 34. REGISTRY SERVICE<br />Conclusions<br />The ARIADNE registry exposes more <br />than 1 million of LOs<br />Federation of registries <br />Optimized management of tools<br />Interoperability with other networks <br />exposing the collection through standards.<br />19<br />
  35. 35. REGISTRY SERVICE<br />Future work (1)<br />Integration of the registry in the federated search layer.<br /><ul><li>Automatic checking of the availability of the SQI targets.
  36. 36. Access rights and user management?
  37. 37. Proposing improves on the different specifications.
  38. 38. How to deal with the repeated instances?</li></ul>20<br />
  39. 39. REGISTRY SERVICE<br />Questions?<br />21<br />

×