Changes between Version 7 and Version 8 of VLO/CMDI data workflow framework


Ignore:
Timestamp:
11/05/15 15:00:49 (9 years ago)
Author:
go.sugimoto@oeaw.ac.at
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • VLO/CMDI data workflow framework

    v7 v8  
    22== VLO/CMDI data workflow framework ==
    33
    4 
    54Note: The same content is also available at GoogleDoc [https://docs.google.com/document/d/1OoxDEFoZKhmotk7tbrElqcn79acKnj4T897sNctMYH8/edit?usp=sharing]
     5Some images are omitted, as they are too big to fit.
    66
    77== Introduction ==
    … …  
    6363
    6464[[Image()]]
    65 [[Image(ConceptMappingInterfaceForm2)]]
    66 [[Image(ConceptMappingInterfaceXML.png)]]
    6765Concept mapping interface in line with the XML code structure
    68 
    69 [[Image(MappingInterfaceForm.png)]]
    70 [[Image(MappingInterfaceFormSelected.png)]]
    71 [[Image(MappingInterfaceForm.2.png)]]
    72 [[Image(MappingInterfaceXML.png)]]
     66[[Image()]]
    7367Value mapping and normalisation interface in line with the XML code structure
    7468
    … …  
    9488{{{OAI-PMH repository / RDF triple store /LOD API}}}
    9589
     90[[Image(Go - VLO data workflow(2).png)]]
     91
    9692After establishing a best practice ingestion data workflow, this phase is rather simple. It can be skipped, if it is not needed or to be incorporated in another phase. In essence, it will add more sophisticated Dissemination Information Package (DIP) module where data records will be stored in more advanced format(s) and could be accessible via different methods.
    9793
    … …  
    10197== Phase III - VLO central service ==
    10298{{{Integration of CLARIN centre services (MD authoring tool) and extra services (Centre Registry, Component Registry, CLAVAS, CCR, and Persistent Identifier) with one Dashboard VLO data management system }}}
     99
     100[[Image(Copy of Go - VLO data workflow_longterm.png)]]
    103101
    104102This is rather an ambitious plan. The phase III is to eliminate redundant services within the VLO framework, and the possibly best solution is to introduce cloud-like central environment where all services are served centrally, and the CLARIN partners will access via two major entry points to manage data in the whole system.