1 / 16

Task 3.2

Task 3.2. LOGOS DO and LO repositories. objectives. This task has to define and implement architecture and services of the Digital Object and Learning Object repositories. A straight approach. Architecture question. This scheme given in WP2.3 suggest two METS instances:

vea
Download Presentation

Task 3.2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Task 3.2 LOGOS DO and LO repositories

  2. objectives This task has to define and implement architecture and services of the Digital Object and Learning Object repositories LOGOS – 1st meeting

  3. A straight approach LOGOS – 1st meeting

  4. Architecture question This scheme given in WP2.3 suggest two METS instances: Is it true ? Will we have two physical repositories ? LOGOS – 1st meeting

  5. Object stored in DO • DO ! • DO relation within a media ? • Ontology ? • Media références (and « CAT »)? LOGOS – 1st meeting

  6. Media services • create Media (URL, CAT) • GetMedia_Annot (mediaID) -> URL annot • SearchMedia (boolean query on CAT) • GETnewMedia() list of non described media LOGOS – 1st meeting

  7. DO services • DO services • Create_DO (DOdesc) • Update_DO (DOdesc) • Delete_DO (DOid) //restricted access • Get_DO(Doid) -> all MD of the DO • Get_all_DO(mediaID) • Get_DO_closure (Doid) ? • Search_DO(GC and MDadmin Filter) • Fuzzy_search (string, Filter) LOGOS – 1st meeting

  8. Ontology’s services • Ontology management services • Checkout_Onto (ONTOid) ->cgxml / lock • Checkin_Onto(OntoId) / unlock • Replace_Onto (OntoId) • Get_Onto (ONTOid) / no lock • Create_Onto (OntoDesc) PB of consistency can occur according the used policy of ontologies forecast in LOGOS LOGOS – 1st meeting

  9. LO Services • Create_LO(Lodesc) • Update_LO(Lodesc) • Delete_LO( LoId) • Get_LO(LOid) • Get_All_DO_in_LO(LOid) • Get_All_LO(DOid*, logic operator) • Search_LO (LOM filters, DOMD) • Fuzzy-search_LO(string, LOMmd , Domd) • Terminology management services ? LOGOS – 1st meeting

  10. Action 1 • Definitive detailed architecture and report (INA / TUC MUSIC/ LIRMM-LERIA) • Fix Objects of the system: LO / DO objects in METS view and their links with the resources • Separate or centralized physical DO/LO repositories ? • Fix DO/LO services • Fix internal components of the repositories and their API (with LERIA) 2 Months LOGOS – 1st meeting

  11. Action (2) • Technological choice for the implementation: • Java / Windows ? • Server platform : J2E • Web services? • Which Database(s)? LOGOS – 1st meeting

  12. Action (3) • Multilingual access: • Multilingual ontologies • Multilingual text capture • Multilingual full text search problem • Dictionaries and correction software on client? 2 months for specs, and tools proposition • Ontology evolution problem LOGOS – 1st meeting

  13. Dependencies • Scenario for internal users of the authoring studio and / or results of ontology production reflexion of T3.1 should help precise some user’s needs in the services définitions. • Media management services inside or outside the scope of this task ? LOGOS – 1st meeting

  14. LOGOS – 1st meeting

  15. Two Mets instances , LOGOS – 1st meeting

  16. Tools dependencies LOGOS – 1st meeting

More Related