Changes between Version 11 and Version 12 of VLO/CMDI data workflow framework

Timestamp:

11/05/15 16:01:30 (9 years ago)

Author:

go.sugimoto@oeaw.ac.at

Comment:

--

VLO/CMDI data workflow framework

@@ -110 +110 @@
 The Dashboard will have an interface to maintain the services (add, delete, edit the components, profiles, concepts, and vocabularies), and the relevant services can be called-up and referenced without visiting another website. For example, when somebody works on the concepts in CCR, the reflection will be dynamically visible in the concept mapping. However, it will not intervene the initial purposes of monitoring the data ingestion pipeline. The VLO curators will still work on the overall data management but they could also access to the abovementioned CLARIN services, if they play two roles. In this way, the communication between data providers and VLO curators is much closer and streamlined in the same framework.
 
-As an option, the Phase III could be implemented with Content Management System (CMS). Strictly speaking, it is not a part of normal VLO data workflow, however, it would be an important development plan, as it is certainly related to VLO record issues (eg. commenting, persistent identifiers, etc). The CMS may work especially well as a end-user management system. If VLO will require more user oriented services, the CMS may make the life of developers easier to manage registered users and user generated content such as tagging, commenting, bookmarking, saved search, uploading, forum, and other social network functionalities. It may also help to quickly build a multilingual website. For more details, please look at Implementing CMS for VLO.
+As an option, the Phase III could be implemented with '''Content Management System (CMS)'''. Strictly speaking, it is not a part of normal VLO data workflow, however, it would be an important development plan, as it is certainly related to VLO record issues (eg. commenting, persistent identifiers, etc). The CMS may work especially well as a end-user management system. If VLO will require more user oriented services, the CMS may make the life of developers easier to manage registered users and user generated content such as tagging, commenting, bookmarking, saved search, uploading, forum, and other social network functionalities. It may also help to quickly build a multilingual website. For more details, please look at Implementing CMS for VLO.
 
 '''Issues to be considered'''