Changes between Version 9 and Version 10 of VLO/CMDI data workflow framework

Timestamp:

11/05/15 15:59:16 (9 years ago)

Author:

go.sugimoto@oeaw.ac.at

Comment:

--

VLO/CMDI data workflow framework

@@ -98 +98 @@
 [[Image(Copy of Go - VLO data workflow_longterm.png)]]
 
-This 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. 
+This is rather an ambitious plan, and should be regarded as a potential. Although it may be a long way to go, it is also good to aim for a more innovative future and we can look back, from the futuristic viewpoint to adjust a course of long-term development strategies. 
+
+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. 
 
 '''The first entry point''' is only for data providers to manage their own data. The MD authoring tool will be separated from the local application and integrated in the central service. This means harvesting is not needed any more. The data will be stored directly on the central storage server and the tool will interact with the VLO dashboard from where necessary information is fetched. A data provider can only manage their metadata (not others) by creating profiles, filling the records, and checking the results visually and statistically. If they already have their metadata sets locally, they will be uploaded to the central environment via OAI-PMH. In terms of digital resources, it should be discussed if they should be deposited in the environment, or in the local storage. Although the latter may be more likely regarded as a hybrid system, in theory, both options will work, as far as the metadata points to the right location of the digital resources (which is already the case). The metadata in the central environment can also be easily exported to the local systems, if required.