Presentation on theme: "Task 3.2 LOGOS DO and LO repositories. INA WP3- T3.2LOGOS – 1st meeting objectives This task has to define and implement architecture and services of."— Presentation transcript:
INA WP3- T3.2LOGOS – 1st meeting objectives This task has to define and implement architecture and services of the Digital Object and Learning Object repositories
INA WP3- T3.2LOGOS – 1st meeting A straight approach
INA WP3- T3.2LOGOS – 1st meeting Architecture question This scheme given in WP2.3 suggest two METS instances: Is it true ? Will we have two physical repositories ?
INA WP3- T3.2LOGOS – 1st meeting Object stored in DO DO ! DO relation within a media ? Ontology ? Media références (and « CAT »)?
INA WP3- T3.2LOGOS – 1st meeting Media services –create Media (URL, CAT) –GetMedia_Annot (mediaID) -> URL annot –SearchMedia (boolean query on CAT) –GETnewMedia() list of non described media
INA WP3- T3.2LOGOS – 1st meeting 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)
INA WP3- T3.2LOGOS – 1st meeting 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
INA WP3- T3.2LOGOS – 1st meeting 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
INA WP3- T3.2LOGOS – 1st meeting Action (2) Technological choice for the implementation: –Java / Windows ? –Server platform : J2E –Web services? –Which Database(s)?
INA WP3- T3.2LOGOS – 1st meeting 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
INA WP3- T3.2LOGOS – 1st meeting 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 ?
Your consent to our cookies if you continue to use this website.