<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>RESEARCH AND DEVELOPMENT WORKSTATION ENVIRONMENT: THE NEW CLASS OF CURRENT RESEARCH INFORMATION SYSTEMS</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>O.V. Palagin</string-name>
          <email>palagin_a@ukr.net</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>V.Yu. Velychko</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>K.S. Malakhov</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>O.S. Shchurov</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Glushkov Institute of Cybernetics of National Academy of Sciences of Ukraine</institution>
          ,
          <addr-line>40 Glushkov ave., Kyiv, Ukraine, 03187. Tel.: (</addr-line>
        </aff>
      </contrib-group>
      <fpage>255</fpage>
      <lpage>269</lpage>
      <abstract>
        <p>Against the backdrop of the development of modern technologies in the field of scientific research, the new class of Current Research Information Systems (CRIS) and related intelligent information technologies have arisen. It was called - Research and Development Workstation Environment (RDWE) - the comprehensive problem-oriented information systems for scientific research and development lifecycle support. The given paper describes design and development fundamentals of the RDWE class systems. The general information model of the RDWE class systems is developed. Also the paper represents the information model of the RDWE class system for supporting research in the field of ontology engineering - the automated building of applied ontology in an arbitrary domain area, scientific and technical creativity - the automated preparation of application documents for patenting inventions in Ukraine. It was called - Personal Research Information System. The main results of our work are focused on enhancing the effectiveness of the scientist's research and development lifecycle in the arbitrary domain area.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>The development of modern technologies increasingly covers the field of intellectual activity and, especially, in
the field of scientific research and development. The new class of Current Research Information Systems and related
intelligent information technologies have arisen that support the main stages of the scientific research and development
lifecycle, starting with the semantic analysis of the information &amp; data material of arbitrary domain area and ending
with the formation of constructive features of innovative proposals. It was called – Research and Development
Workstation Environment (RDWE) – the comprehensive problem-oriented information systems for scientific research
and development support. A distinctive feature of such systems and technologies is the possibility of their problematic
orientation to various types of scientific research and development by combining on a variety of functional services and
adding new ones within the Cloud-integrated Environment (inside the Ubuntu open source operating system as the
integrating cloud environment for instance).</p>
    </sec>
    <sec id="sec-2">
      <title>Current research information systems</title>
      <p>
        The EuroCRIS [
        <xref ref-type="bibr" rid="ref11">3</xref>
        ] organization was founded in 2002, is an international not-for-profit association, that brings
together experts on research information in general and research information systems. The mission of EuroCRIS is to
promote cooperation within and share knowledge among the research information community and interoperability of
research information through CERIF [
        <xref ref-type="bibr" rid="ref12">4</xref>
        ] – the Common European Research Information Format. Areas of interest also
cover research databases, CRIS related data like scientific datasets, (open access) institutional repositories, as well as
data access and exchange mechanisms, standards and guidelines and best practice for CRIS. The EuroCRIS provides
the framework for the flow of information/data between a broad variety of stakeholders: researchers, research managers
and administrators, research councils, research funders, entrepreneurs, and technology transfer organizations.
      </p>
      <p>
        The basic user categories of modern CRIS and their information demands are listed in [
        <xref ref-type="bibr" rid="ref13">5</xref>
        ] and represented in
      </p>
      <sec id="sec-2-1">
        <title>Search for scientific results, collaborators, equipment and material resources,</title>
        <p>
          projects financing. Easy access to relevant information and associated
software, processor power, storage systems and detectors to collect more data
to overcome incomplete or inconsistent information – the paradigm of
Service-Oriented Science (SOS) in which web services are virtual access
points to data, computational resources, R&amp;D environments [
          <xref ref-type="bibr" rid="ref14">6</xref>
          ].
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Implementation of the recent research results in the educational process and mastering of research results in the learning process. The organization of service support of e-learning at the university, especially at the replaced university [7]. Applying to the educational process the modern paradigm of</title>
        <p>Service-Oriented Learning (SOL) implemented as Personal Learning
Environments, Virtual Learning Environments, Learning Management
Systems, Education-as-a-Service models, and Cloud Learning Environments –
using RDWE systems as an E-learning/education-oriented environment.</p>
      </sec>
      <sec id="sec-2-3">
        <title>Research management and administration, statistical reporting on recent achievements, determining the role of research institutes and researchers in the research process.</title>
      </sec>
      <sec id="sec-2-4">
        <title>Project reports, estimation of expected and obtained research results.</title>
      </sec>
      <sec id="sec-2-5">
        <title>Research processes coordination, search for collaborators and search for research funders for project financing.</title>
      </sec>
      <sec id="sec-2-6">
        <title>Searching for technology, engineering, and hunting experts who can evaluate the technology.</title>
      </sec>
      <sec id="sec-2-7">
        <title>Acquisition information and data in the accessible form for perception and</title>
        <p>understanding.</p>
        <p>This user’s groups and their information demands determine the main types of information/data sources that
CRIS works with: progress reports, project results reports, personal information and data, scientific publication,
organizations, projects, research results, technology and engineering, patents, fund programs, expert assessments,
digital libraries, encyclopedias and dictionaries, websites, mailing lists, social networks, databases, computing
resources, technological normative and other documents, educational and museum resources. Also, this user’s groups
and their information demands determine the main types of services provided by CRIS: reuse of scientific
developments, methodologies, and technologies; information search; targeted dissemination of information; messages
services; bridging of horizontal and vertical relations between organizations; backup data storage and archival
information/data repository; support for the educational process; providing analytical services.</p>
        <p>
          Requirements for CRIS in the information management aspect of strategic research management has been
analyzed in [
          <xref ref-type="bibr" rid="ref15">8</xref>
          ], which describes the types of research managerial activities, introduces the currently available
information sources and how the information found in these is applied today.
        </p>
        <p>
          The paper [
          <xref ref-type="bibr" rid="ref16">9</xref>
          ] describes requirements for CRIS to effective dissemination of technologies, the management of
scientific programs and functioning of funds for research funding. Noted the importance of CRIS systems to collaborate
 identify funding sources for R&amp;D;
 find partners to cooperate in R&amp;D activities and share expertise;
 form transnational consortia for exploitation of research results;
 promote and locate transferable technologies, and more.
researchers and to support the information functioning of funds. Also represented the basic lifecycle of scientific
programs and the information demands of participants at each phase of the cycle.
        </p>
        <p>
          The CORDIS [
          <xref ref-type="bibr" rid="ref17">10</xref>
          ] portal emphasized the basic use cases of scientific portals for researchers:
 keep up-to-date on current research findings and strategic directions;
        </p>
        <p>In the field of scientific communication and collaboration next tools are used: telecommunications services of
direct interaction (video chat, video conference, voice calls, text and video messages) – Skype, Viber, VSee etc.;
cloudbased sets of team collaboration tools and services – Slack etc.; web conference platforms for various types of online
collaborative services including webinars, webcasts, and peer-level web meetings – Adobe Connect etc.; services of
indirect communication – email; social services on the Internet – social networks with instant messaging such as
Facebook and Telegram. These services are widespread with off-the-shelf software and in the availability of
communication bus with sufficient bandwidth allow instant scientific communication.</p>
        <p>CRIS can include systems that combine social network technologies as well as usual file repository technologies.
As commercial projects, such CRIS is oriented to one of the following business models:</p>
        <p>
          - to sell user’s and subscriber’s data to advertisers that provide targeted ads, which usually costs more than
usual. Also, the platform offers universities and corporations the option to post job listings for free, but generates
revenue by charging some money for increased visibility (ResearchGate) [
          <xref ref-type="bibr" rid="ref18 ref19">11, 12</xref>
          ];
        </p>
        <p>
          - to carry out analytics for the uploaded content and recommend suitable research activity for a fee. Also, the
platform generates revenue by providing trending research data to R&amp;D institutions that can improve the quality of their
decisions (Academia.edu) [
          <xref ref-type="bibr" rid="ref19 ref20">12, 13</xref>
          ];
        </p>
        <p>
          - to provide additional paid services for storage of data (publications, raw data, and media files) – the
individual researcher is served with a freemium model, users can upgrade their cloud space for a monthly fee; to
organize online discussion community platforms, forums for sharing and discussing research. Also, the platform offers
real-time analytics to libraries for a fee and has opened its application programming interface (API) for programmers
who build third-party apps on top of the data generated across the platform (Mendeley) [
          <xref ref-type="bibr" rid="ref19 ref21">12, 14</xref>
          ].
        </p>
        <p>According to demands of the scientific community members Academia.edu and ResearchGate provide the
following basic features for registered users:
members may “follow” a research interest, in addition to following other individual members;
allows its users to create a profile, upload their work(s), select areas of interests;
- platform indexes self-published information on user profiles to suggest members connect with others who
have similar interests.</p>
        <p>private chat rooms where users can share data, edit shared documents, or discuss confidential topics;
a research-focused job board feature;</p>
      </sec>
      <sec id="sec-2-8">
        <title>ResearchGate publishes a citation impact measurement in the form of an “RG Score”;</title>
        <p>- Academia.edu proclaims it supports the open science or open access movements and instant distribution of
research, and a peer-review system that occurs alongside distribution, instead of prior to it.</p>
        <p>However, the Academia.edu service is not designed to provide comprehensive information support for scientific
research, and users, in general, posts published articles to the system. Unlike Academia.edu, ResearchGate has more
diverse features. People that wish to use the site need to have an email address at a recognized institution or to be
manually confirmed as a published researcher to sign up for an account. Members of the site each have a user profile
and can upload research output including papers, data, chapters, negative results, patents, research proposals, methods,
presentations, and software source code. Users may also follow the activities of other users and engage in discussions
with them. Users are also able to block interactions with other users. ResearchGate has a blogging feature for users to
write short reviews on peer-reviewed articles. When a member posts a question, it is fielded to others that have
identified on their user profile that they have a relevant expertise.</p>
        <p>The social networking Internet services Academia.edu and ResearchGate are largely aimed at forming the
socalled “name” of the scientist and serving a research-focused job board feature.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>General design principles (approaches) of the CRIS-like systems for scientific R&amp;D support</title>
      <p>
        There are different approaches to define the structure of research activities and the research lifecycle [
        <xref ref-type="bibr" rid="ref22 ref23">15, 16</xref>
        ].
The review of these approaches, as well as the analysis of research activities, allows defining its basic types, which
regulate its structure and are invariant in relation to the domain area, content, methods, and approaches of the research
activity. The basic types of research activities are [
        <xref ref-type="bibr" rid="ref23">16</xref>
        ]:
- Descriptive vs. Analytical: Descriptive research includes surveys and fact-finding enquiries of different
kinds. The major purpose of descriptive research is the description of the state of affairs as it exists at present. In social
science and business research, we quite often use the term Ex post facto research for descriptive research studies. The
main characteristic of this method is that the researcher has no control over the variables; he can only report what has
happened or what is happening. Most ex-post facto research projects are used for descriptive studies in which the
researcher seeks to measure such items as, for example, the frequency of shopping, preferences of people, or similar
data. Ex post facto studies also include attempts by researchers to discover causes even when they cannot control the
variables. The methods of research utilized in descriptive research are survey methods of all kinds, including
comparative and correlational methods. In analytical research, on the other hand, the researcher must use facts or
information already available and analyze these to make a critical evaluation of the material;
      </p>
      <p>- Applied vs. Fundamental: Research can either be applied (or action) research or fundamental (to basic or
pure) research. Applied research aims at finding a solution for an immediate problem facing a society or an
industrial/business organization, whereas fundamental research is mainly concerned with generalizations and with the
formulation of a theory. Research concerning some natural phenomenon or relating to pure mathematics are examples
of fundamental research. Similarly, research studies, concerning human behavior carried on with a view to generalize
about human behavior, are also examples of fundamental research, but research aimed at certain conclusions (say, a
solution) facing a concrete social or business problem is an example of applied research. Research to identify social,
economic, or political trends that may affect an institution or the copy research (research to find out whether certain
communications will be read and understood) or the marketing research or evaluation research are examples of applied
research. Thus, the central aim of the applied research is to discover a solution for some pressing practical problem,
whereas basic research is directed towards finding information that has a broad base of applications and thus, adds to
the already existing organized body of scientific knowledge;</p>
      <p>- Quantitative vs. Qualitative: Quantitative research is based on the measurement of quantity or amount. It is
applicable to phenomena that can be expressed in terms of quantity. Qualitative research, on the other hand, is
concerned with the qualitative phenomenon, i.e., phenomena relating to or involving quality or kind. For instance, when
we are interested in investigating the reasons for human behavior (i.e., why people think or do certain things), we quite
often talk of ‘Motivation Research’, an important type of qualitative research. This type of research aims at discovering
the underlying motives and desires, using in-depth interviews for the purpose. Other techniques of such research are
word association tests, sentence completion tests, story completion tests and similar other projective techniques.
Attitude or opinion research i.e., research designed to find out how people feel or what they think about a subject or
institution is also qualitative research. Qualitative research is especially important in the behavioral sciences where the
aim is to discover the underlying motives of human behavior. Through such research, we can analyze the various
factors which motivate people to behave in a manner or which make people like or dislike a thing. It may be stated,
however, that to apply qualitative research in practice is relatively a difficult job and therefore, while doing such
research, one should seek guidance from experimental psychologists;</p>
      <p>- Conceptual vs. Empirical: Conceptual research is that related to some abstract idea(s) or theory. It is
generally used by philosophers and thinkers to develop new concepts or to reinterpret existing ones. On the other hand,
empirical research relies on experience or observation alone, often without due regard for system and theory. It is
databased research, coming up with conclusions which are capable of being verified by observation or experiment. We can
also call it as the experimental type of research. In such a research, it is necessary to get at facts firsthand, at their
source, and actively to go about doing certain things to stimulate the production of desired information. In such a
research, the researcher must first provide himself with a working hypothesis or guess as to the probable results. He
then works to get enough facts (data) to prove or disprove his hypothesis. He then sets up experimental designs which
he thinks will manipulate the persons or the materials concerned so as to bring forth the desired information. Such
research is thus characterized by the experimenter’s control over the variables under study and his deliberate
manipulation of one of them to study its effects. Empirical research is appropriate when the proof is sought that certain
variables affect other variables in some way. Evidence gathered through experiments or empirical studies is today
considered to be the most powerful support possible for a given hypothesis;</p>
      <p>- Some Other Types of Research: All other types of research are variations of one or more of the above-stated
approaches, based on either the purpose of research, or the time required to accomplish research, on the environment in
which research is done, or based on some other similar factor. Form the point of view of time, we can think of research
either as one-time research or longitudinal research. In the former case, the research is confined to a single time-period,
whereas in the latter case the research is carried on over several time-periods. Research can be field-setting research or
laboratory research or simulation research, depending upon the environment in which it is to be carried out. Research
can as well be understood as clinical or diagnostic research. Such research follows case-study methods or in-depth
approaches to reach the basic causal relations. Such studies usually go deep into the causes of things or events that
interest us, using very small samples and very deep probing data gathering devices. The research may be exploratory or
it may be formalized. The objective of exploratory research is the development of hypotheses rather than their testing,
whereas formalized research studies are those with substantial structure and with specific hypotheses to be tested.
Historical research is that which utilizes historical sources like documents, remains, etc. to study events or ideas of the
past, including the philosophy of persons and groups at any remote point of time. Research can also be classified as</p>
      <p>4.
and forums).</p>
      <p>1.
2.
conclusion-oriented and decision-oriented. While doing conclusion-oriented research, a researcher is free to pick up a
problem, redesign the enquiry as he proceeds and is prepared to conceptualize as he wishes. Decision-oriented research
is always for the need of a decision maker and the researcher, in this case, is not free to embark upon research according
to his own inclination. Operations research is an example of decision-oriented research since it is a scientific method of
providing executive departments with a quantitative basis for decisions regarding operations under their control.</p>
      <p>
        The general principle that should be considered when designing CRIS-like systems for scientific research and
technical research creativity support is that the system must fully cover all the basic types of research activities,
implement the full research lifecycle. Based on this basic principle can identify the main entities of CRIS-like
systems [
        <xref ref-type="bibr" rid="ref24">17</xref>
        ]:
      </p>
      <sec id="sec-3-1">
        <title>User with all related attributes.</title>
      </sec>
      <sec id="sec-3-2">
        <title>Organizations which are related to users. Organizations and foundations (research funders etc.) that provide grant support for scientific research. Scientific communities with the ability to carry on a discussion between united users (analogues of chats</title>
      </sec>
      <sec id="sec-3-3">
        <title>Scientific journals and publishers.</title>
      </sec>
      <sec id="sec-3-4">
        <title>Bibliographies that can be created both by the users themselves and by the communities.</title>
      </sec>
      <sec id="sec-3-5">
        <title>Publications of users that can be linked to publishers and periodicals.</title>
        <p>
agents etc.;</p>
        <p>
8. Projects that can integrate users, bibliographies, documents, and general data, and can also be related to
grants of research funders and organizations.</p>
        <p>It should be noted that all these and other entities that may appear in the future should be able to communicate
with each other. This communication will allow the flexible and comprehensive solution of the tasks of organizing of
co-operative research activities by communities of scientists, to receive various reports, for example, lists of
publication, lists of publisher’s journals, statistical reports on the research activity of employees, etc. The integrated
system should be a universal instrument or utility toolkit not only for the purposes of supporting scientific research
but also for the analysis of the activities of scientific organizations, foundations, and publishers.</p>
        <p>
          Another important principle for developing the CRIS-like system is the choice of a user identification model.
There is no need to create multiple user accounts in different network services. For identification, it is suitable to
choose one of the open identifying system: Open Researcher and Contributor ID (ORCID) [
          <xref ref-type="bibr" rid="ref25">18</xref>
          ], ResearcherID [
          <xref ref-type="bibr" rid="ref26">19</xref>
          ]
or OpenID [
          <xref ref-type="bibr" rid="ref27">20</xref>
          ]. For scientists, it is suitable to choose ORCID – is a nonproprietary alphanumeric code to uniquely
identify scientific and other academic authors and contributors. It is implemented in the open project ORCID. The
ORCID organization offers an open and independent registry intended to be the de facto standard for contributor
identification in research and academic publishing. The ORCID community includes everyone in the research
community who recognizes the need for researchers to be uniquely identified and connected with their contributions
and affiliations. This means individual researchers, organizations involved in research – universities, laboratories,
commercial research companies, research funders, publishers, patent offices, data repositories, professional societie s,
and more – as well as organizations that build systems that support information management among and between
these groups. Third-party tools allow the migration of content from other services into ORCID, for example ,
Mendeley2ORCID, for Mendeley.
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>General requirements to the CRIS-like systems for scientific R&amp;D support</title>
      <p>interactive user input;</p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref12 ref24 ref28">4, 17, 21</xref>
        ] reviewed general requirements and specifications for the CRIS-like systems. Summing up all these
papers and resources, we can point out the most general requirements and specifications for the CRIS-like systems.
      </p>
      <p>1. Data coverage. Coverage of the maximum amount of information resources and repositories. It is
necessary to create data input procedures and data entry points to collect information. The following options for
inputting data are available:

data collection over the Internet uses the specialized software – web crawlers, Internet bots, intelligent
data exchange and CRIS integration with other CRIS-like systems.</p>
      <p>2. Data relevance. The automatic collection of information over the Internet may accumulate out of date data.
This problem can be solved by:
</p>
      <p>to create detailed formats for submitting metadata about resources, directories for thematic
classification of resources, as well as adding metadata to resources. It is problematic to require authors clearly and
accurately comply with the metadata formats and carefully add metadata to text sources that require additional work
and explore metadata formats;
</p>
      <p>to classify and categorize all the information resources collected by experts (users) and web crawlers.
Also, to indicate the degree of probability of belonging to the search query depending on its source;
for the automated search engines – the restriction activity area of the web crawler to collect information;
for input data exchange with other systems – by establishing precise filters for imported information
for all systems – verification and classification of the input data.</p>
      <p>4. The maintenance of the intelligent user query service. User query services should support search by
attributes, resource overviews by category, and full-text search using semantic document analysis.</p>
      <p>5. Support various levels of abstraction for data representation. Internet efficiency for CRIS-like systems is
not a direct consequence of the amount of available information/data or even its quality but is a direct consequence of
the rate and accuracy of the selection of information for the demands of researchers. Support various levels of
abstraction for information/data representation allows precipitating the information/data search without its loss.
CRISlike systems need to support several levels of abstraction, and not just full-text descriptions. It is necessary to represent
information in a compact form (document ontology, abstract, annotation, compendium, or recap) selectively – from
brief descriptions for the maximum quick search to very detailed descriptions of information objects.</p>
      <p>6. The historicity of the scientific information. The specificity of the scientific information is quite a short
period of its relevance. For many types of the scientific information resources, it is important to keep the description of
the lifecycle of these resources and be able to restore the status of the resource at any given time.</p>
      <p>7. Maintaining an archival repository of scientific information. As it was noted above, the most part of the
scientific information fast becomes outdated. But there are information resources that may be relevant for a long time.
These include: the long-term documents, the patents, and the multimedia information about historical events. Scientific
reports of institutes, speeches of scientists and researchers can also have a huge historical value, becoming later even
more valuable. Therefore, the system should support the possibility of long-term storage of the information resources.</p>
      <p>
        8. Distributed architectures support for the information systems. This requirement is a prerequisite for
completeness, authenticity, and relevance of information. The experience of usage of the CRIS-like systems has shown
that it is difficult to implement, and in many cases, even impossible, the creation of centralized scientific systems that
covers scientific information in some domain area of science, or in some country. In [
        <xref ref-type="bibr" rid="ref29">22</xref>
        ] Hale University researchers
have proven proposals for the creation of administrative and technical mechanisms for the functioning of virtual
distributed scientific libraries. In terms of the distributed computing environment, CRIS-like systems meet the
following requirements:

information exchange protocols support with other information systems;
accepted metadata standards support for the export/import of data and the usage of metadata to describe
and to specify resources;

information verification feature;
linking to internal resources support for both: in user interfaces and at the system level;
online service for accessing links to other websites and documents;
selection of resources in the intellectual process, according to published quantitative and thematic
availability of descriptions of the resource’s content in the range from brief annotation to detailed
the exact indication of the search area to the search engines, as well as the criteria for the quality of the
collected information;

      </p>
      <p>to create the ontologies of resources according to the user demands. The classification of resources by
experts in accordance with these ontologies.</p>
      <p>for interactive input – the restriction of input only by authenticated users;
3. Completeness and validity of data. The data completeness problem is solved by the same method as the
coverage data problem solved. The validity of data problem can be solved by:
</p>
      <p>intelligently created structure or scheme for navigation in the resource space. A good example of such
structure can be an ontological scheme of resources.</p>
      <p>For some domain areas of research, it is also important that the scientific information system provides the ability
to use computational resources that are based on generally accepted standards.</p>
      <p>
        The basic concepts of the workstation environment (WE) consider to [
        <xref ref-type="bibr" rid="ref30">23, 24</xref>
        ] are – is an individual complex of
information resources, software, hardware, organizational and technological facilities (tools) for individual or collective
usage, united to perform certain functions of the employee. WE provide the worker with all the tools and facilities
necessary to perform certain functions.
      </p>
      <p>to solve a certain class of tasks and problems, united by a common information processing technology;
 to formalize professional knowledge – the possibility of providing with the help of WE the automation
of new functions and solving new tasks in the process of accumulation of experience with the system;
to automate data processing in a specific area of activity;
to provide user access to the set of software; hardware and information tools &amp; facilities;
 to create custom comfortable working conditions and friendly user interface to communicate &amp; interact
with the system;</p>
      <p> to combine the system with other elements of information processing and modification, expansion
capabilities of WE without interrupting its operation.</p>
      <p>The structure and composition of the elements of any WE depend on its purpose, the composition of tasks,
structure, software, the method of fixing data in primary documents and more. The WE structure is composed of:
- the information support part of WE. This is a set of facilities and methods for building an information
base, which is divided into a machine and internal machine.</p>
    </sec>
    <sec id="sec-5">
      <title>General principles of the Research and Development Workstation Environment design</title>
      <p>Scientific and research communities create networks that combine digital libraries, file repositories, archival
information/data repositories, web servers with scientifically relevant information. The key objective factor that must
be taken into account when designing, developing and using the workstation for the Ukrainian researcher is the
limited financial resources appropriated for the development and maintenance of the workplace software, which
results in the following consequences: the inability to involve the necessary number of specialists to the development
process; minimizing the costs of the software implementing, maintaining and updating; system development for
several years by the group of developers whose composition (body) is changing; the necessity to maximize the reuse
of software that has already been developed. Next we define the general development principles of the RDWE and
its components.</p>
      <p>
        1. Modular design. The development of any information system, especially that aimed at solving the
complex variety of problems and tasks, should be based on a modular design principle [
        <xref ref-type="bibr" rid="ref24">17</xref>
        ]. Modular design, or
“modularity in design”, is a design approach that subdivides a system into smaller parts called modules or skids, that
can be independently created and then used in different systems. A modular system can be characterized by
functional partitioning into discrete scalable, reusable modules; rigorous use of well -defined modular interfaces; and
making use of industry standards for interfaces. When creating a modular system, instead of creating a monolithic
application (where the smallest component is the whole), several smaller modules are written separately so that,
when composed together, they construct the executable application program. Typically, these are also compiled
separately, via separate compilation, and then linked by a linker. A just-in-time compiler may perform some of this
construction “on-the-fly” at runtime. This makes modular designed systems if built correctly, far more reusable than
a traditional monolithic design, since all (or many) of these modules may then be reused (without change) in other
projects.
      </p>
      <p>
        2. Microservices-based architecture (MSA). Microservices is a variant of the service-oriented architecture
architectural style that structures an application as a collection of loosely coupled services [
        <xref ref-type="bibr" rid="ref31">25</xref>
        ]. In MSA, services
should be fine-grained and the protocols should be lightweight. The benefit of decomposing an application into
different smaller services is that it improves modularity and makes the application easier to understand, develop and
test. There is no industry consensus yet regarding the properties of microservices, and an official definition is
missing as well. Some of the defining characteristics that are frequently cited include [
        <xref ref-type="bibr" rid="ref32">26</xref>
        ]: services in MSA are often
processes that communicate with each other over a network in order to fulfill a goal using technology-agnostic
protocols such as HTTP; services in MSA should be independently deployable; services are easy to replace; services
are organized around capabilities, e.g., user interface front-end, recommendation, logistics, billing, etc.; services can
be implemented using different programming languages, databases, hardware and software environme nt, depending
on what fits best; services are small in size, messaging enabled, bounded by contexts, autonomously developed ,
independently deployable, decentralized and built and released with automated processes.
      </p>
      <p>3. Сross-platform software (also multi-platform software or platform-independent software). The
researcher must have access to the services provided by the RDWE from various types of devices operating under
the control of various operating systems. One of the ways to achieve this goal can be access to services through an
adaptive user interface of the web applications. Web applications are typically described as cross-platform because,
ideally, they are accessible from any of various web browsers within different operating systems. Such applications
generally employ a client-server system architecture and vary widely in complexity and functionality. This wide
variability significantly complicates the goal of cross-platform capability, which is routinely at odds with the goal of
advanced functionality. Basic web applications perform all or most pro cessing from a stateless server and pass the
result to the client web browser. All user interaction with the application consists of simple exchanges of data
requests and server responses. Implementation mechanisms:</p>
      <p>
        Node.js [
        <xref ref-type="bibr" rid="ref33">27</xref>
        ] server platform – is an open-source, cross-platform JavaScript run-time environment for
executing JavaScript code server-side. Node.js enables JavaScript to be used for server-side scripting and runs scripts
server-side to produce dynamic web page content before the page is sent to the user's web browser. Consequently,
Node.js has become one of the foundational elements of the “JavaScript everywhere” paradigm, allowing web
application development to unify around a single programming language, rather than rely on a differ ent language for
writing server-side scripts. Node.js brings event-driven programming to web servers, enabling development of fast
web servers in JavaScript. Developers can create highly scalable servers without using threading, by using a
simplified model of event-driven programming that uses callbacks to signal the completion of a task. Node. js
connects the ease of a scripting language (JavaScript) with the power of Unix network programming. Node.js
applications can run on most modern operating systems (Linux, macOS, Microsoft Windows and Unix servers) and
hardware platforms (x86, x64, ARMv6, ARMv7, ARMv8).
      </p>
      <p></p>
      <p>The adaptive user interface of the web application with responsive web design using Pug (is a
template engine for Express), Bootstrap (is a design and style framework), JQuery library and AJAX (an approach to
building user interfaces for web applications) – is a web design approach aimed at crafting the visual layout of sites
to provide an optimal viewing experience – easy reading and navigation with a minimum of resizing, panning, and
scrolling – across a wide range of devices, from mobile phones to desktop computer monitors.
</p>
      <p>Storage service powered by MongoDB – is a free and open-source cross-platform document-oriented
database program. Classified as a NoSQL database program, MongoDB uses JSON -like documents with schemas.</p>
      <p>
        4. JSON/XML data model and REST architectural style (RESTful web services). JavaScript Object Notation
or JSON – is an open-standard file format that uses human-readable text to transmit data objects consisting of
attribute-value pairs and array data types (or any other serializable value). It is a very common data format used for
asynchronous browser-server communication. JSON standard defines a metalanguage, based on which, by imposing
restrictions on the structure and content of documents, specific, domain-oriented markup languages are determined.
The author of the document creates its structure, builds the necessary links between the elements, and uses those
commands that meet its requirements and asks for the type of markup that it needs to handle the documents. Creating
the correct structure of the information exchange mechanism at the beginning of the system project development,
many future problems can be avoided due to the incompatibility of the data formats that are used by the various
components of the system. Representational state transfer (REST) [
        <xref ref-type="bibr" rid="ref34">28</xref>
        ] or RESTful web services are a way of
providing interoperability between computer systems on the Internet. REST -compliant Web services allow
requesting systems to access and manipulate textual representations of Web resour ces using a uniform and
predefined set of stateless operations. In a RESTful Web service, requests made to a resource's URI will elicit a
response that may be in XML, HTML, JSON or some other defined format. The response may confirm that some
alteration has been made to the stored resource, and it may provide hypertext links to other related resources or
collections of resources. Using HTTP, as is most common, the kind of operations available include those predefined
by the HTTP methods GET, POST, PUT, DELETE and so on. The RESTful architectural style possesses the
following constraints [
        <xref ref-type="bibr" rid="ref35">29</xref>
        ]:

      </p>
      <p>Client/Server: Separation of concerns, exemplified by a client–server architecture. The idea is that
different components can evolve independently—the user interface in the client can evolve separately from the
server, and the server is simpler.</p>
      <p></p>
      <p>Cacheable: Data in a response (a response to a previous request) is labeled as cacheable or
noncacheable. If it is cacheable, the client (or an intermediary) may reuse that for the same k ind of request in the future.
</p>
      <p>Uniform Interface: There is a uniform interface between components. In practice, there are four
interface constraints: resource identification – requests identify the resources they are operating on (by a URI, for
example); resource manipulation through the representation of the resource – when a client or server that has access
to a resource, it has enough information based on understanding the representation of the resource to be able to
modify that resource; messages are self-descriptive – the message contains enough information to allow a client or
server to handle the message, this is normally done through the use of Internet Media types (MIME types); use of
hypermedia to change the state of the application – for example, the server provides hyperlinks that the client uses to
make state transitions.</p>
      <p></p>
      <p>Stateless: The client–server interaction is stateless. There is no stored context on the server. Any
session information must be kept by the client.</p>
      <p></p>
      <p>Layered System: Components are organized in hierarchical layers; the components are only aware of
the layer within which the interaction is occurring. Thus, a client connecting to a server is not aware of any
intermediate connections. Intermediate filter components can change the message while it is in transit: because the
message is self-descriptive and the semantics are visible, the filter components understand enough about the message
to modify it.</p>
      <p></p>
      <p>Code on Demand: Code on demand is optionally supported, that is, clients can download scripts that
extend their functionality.</p>
      <p>5. Free/Libre and open-source software (FLOSS). FLOSS is software that can be classified as both free
software and open-source software. That is, anyone is freely licensed to use, copy, study, and change the software in
any way, and the source code is openly shared so that people are encouraged to voluntarily improve the design of the
software. The benefits of using FLOSS can include decreased software costs, increased security, and stability
(especially regarding malware), protecting privacy, and giving users more control over their own hardware. The use
of free software will significantly save money at the stages of development and implementation of the RDWE.</p>
      <p>
        6. Cloud computing. Cloud computing [
        <xref ref-type="bibr" rid="ref36">30</xref>
        ] can provide interaction between different CRIS-like systems
(such as RDWE) over the Internet, with the optimal distribution of load between local and remote servers. In cloud
computing paradigm, computer resources and capacity available to the user as Internet servic es for data processing.
Cloud-computing providers offer their “Services” according to different models, of which the three standard models
per NIST (The National Institute of Standards and Technology) [
        <xref ref-type="bibr" rid="ref37">31</xref>
        ] are Infrastructure as a Service (IaaS), Platform
as a Service (PaaS), and Software as a Service (SaaS). These models offer increasing abstraction; they are thus often
portrayed as a layer in a stack: infrastructure-, platform- and software-as-a-service, but these need not be related.
      </p>
      <p>7. Data storage based on the abstraction of data repository. Abstraction of software modules from the
implementation of data storage technology allows the system administrator to choose the type of data repository,
which is maximally adapted for the purposes of the specific RDWE configuration.</p>
      <p>8. Data repositories synchronization. The ability of the off-line operations of the RDWE and data
synchronization with the central data repository. This is important in the absence of a permanent network connection.
This feature implemented with the internal mechanisms for replication of the data repository.</p>
    </sec>
    <sec id="sec-6">
      <title>General information model of the Research and Development Workstation Environment</title>
      <p>The RDWE class system’s generalized information model represented as a three-tuple composite web service
(CWS) using the revised formalism given in [32]:</p>
      <p>CWS  AWS ,F ,CIEnv ,
AWS  awsi i  1, m</p>
      <p>is a set of atomic web services (problem-oriented microservices and FLOSS
mN
applications; personalized FLOSS applications) available for usage. The AWS set consists of the problem-oriented
atomic web services aws and each of them can be designed and developed as a microservice or a desktop application,
that allows them to be used as an independent software separately from the RDWE and as its components inside CIEnv ;
is a set of functions, the functional filling-up of the RDWE, each function is the
F  AWS:C j j  1,n</p>
      <p>nN
result of coordination and interaction of the AWS elements;</p>
      <p>C j  AWS ,C j  awsk k  1,k  m</p>
      <p>kN
j -th function of CWS ;</p>
      <p>is a subset of atomic web services that are required to implement the</p>
      <p>
        CIEnv   prl ,mid ,os,crd ,typicalFLOSS  is a set of elements (represented as layers) that combine into the
Cloudintegrated Environment (CIE);
prl – physical resource layer represents physical hardware and facility resources;
mid – middle layer (using in the concepts of cloud service orchestration model [
        <xref ref-type="bibr" rid="ref36">30</xref>
        ]) represents resource
abstraction and control layer. It is supposed to use OpenStack software platform;
      </p>
      <p>os – operating system layer represents guest operating system. It is supposed to use Ubuntu server with LXDE
(abbreviation for Lightweight X11 Desktop Environment) desktop environment or Xfce desktop environment. Atomic
web services work on the operating system layer – awsi  os ;</p>
      <p>crd – coordination component. The crd function is to coordinate atomic web services in CWS , and by the
coordination procedure we will understand the execution of invocation of some awsk  C j in the defined sequence. The
coordination component crd can be implemented as the reverse proxy server of tasks. Nginx also is a part of crd –
used as front-end to control and protect access to the server on a private network, performs tasks such as
loadbalancing, authentication, decryption, and caching.</p>
      <p>typicalFLOSS – a typical FLOSS layer includes some regular application suit needed for the scientific research
and development lifecycle (regular software suit may change in the future): LibreOffice office suite; Mozilla Firefox
and Chromium web browsers; Sylpheed email client; Sublime Text 2 and jEdit source code editors; Wine compatibility
layer that aims to allow computer programs developed for Microsoft Windows to run on Unix-like operating systems;
Python (SciPy Python library used for scientific computing and technical computing); R environment for statistical
computing and graphics; Eclipse integrated development environment; Redmine project management and issue tracking
tool; X2Go remote desktop software.</p>
      <p>CIE of RDWE delivers to researchers (to researcher’s client device – laptop, desktop, mobile or tablet) using the
extended Platform-as-a-Service service delivery model via X2Go remote desktop software and ssh cryptographic
network protocol (picture).</p>
      <sec id="sec-6-1">
        <title>Picture. Cloud-integrated Environment of RDWE delivery model</title>
        <p></p>
      </sec>
      <sec id="sec-6-2">
        <title>Linux;</title>
      </sec>
      <sec id="sec-6-3">
        <title>MacOS 10.9 Mavericks and higher were tested.</title>
        <p>To take all features of CIE, the researcher’s client device (laptop or desktop) must run latest stable release of
X2Go remote desktop software and comply with the following system requirements.</p>
        <p>X2Go Client is part of Ubuntu 12.04 &amp; later, Fedora 19 and later, Raspbian Wheezy &amp; Jessie. X2Go Client is
currently only released as a 32-bit x86 build. Both 32-bit x86 and 64-bit x86 versions of Windows are supported:
Windows XP 32-bit SP3 (deprecated); Windows XP 64-bit SP2 (deprecated); Windows Vista SP2; Windows 7 SP1;
Windows 8.1 (with “Update 1”); Windows 10 (1607).</p>
        <p>Connecting to the CIE via ssh, the researcher’s client device (laptop or desktop) must comply with the following
system requirements:
</p>
        <p>Windows XP 32-bit SP3,64-bit SP2; Vista SP2, 7 SP1, 8.1 (with “Update 1”), 10 (1607) with PuTTY
terminal emulator installed;
</p>
        <p>Software implementation of the RDWE class systems is carried out using software specific to the chosen domain
area and may be different from the one above.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>Personal Research Information System – Research and Development Workstation</title>
    </sec>
    <sec id="sec-8">
      <title>Environment for ontology engineering and scientific creativity support</title>
      <p>The main feature of the RDWE class systems is the problem orientation to an arbitrary domain area. As part of
the research and development work of the Glushkov Institute of Cybernetics of National Academy of Sciences of
Ukraine (Department of Microprocessor Technology) has developed and implemented the software system in its class.
It was called – Personal Research Information System (PRIS) [33] – the RDWE class system for supporting research in
the field of ontology engineering (the automated building of applied ontology in an arbitrary domain area as a main
feature), scientific and technical creativity (the automated preparation of application documents for patenting inventions
in Ukraine as a main feature). In accordance with the fundamental information model of the RDWE systems, the PRIS
information model was developed.</p>
      <p>
        At the actual stage of PRIS system development the AWS set consists of the following aws (natural language
processing (NLP) functions are available for the Ukrainian language):
aws1 – RESTful web service for converting PDF files to plain/text. Available via GitHub repository [
        <xref ref-type="bibr" rid="ref38">34</xref>
        ].
aws2 – RESTful web service for converting DOC/DOCX files to plain/text. Available via GitHub repository [
        <xref ref-type="bibr" rid="ref39">35</xref>
        ].
aws3 – RESTful web service for language identification.
aws4 – RESTful web service for automatic plain/text summarization. Available via GitHub repository [
        <xref ref-type="bibr" rid="ref40">36</xref>
        ].
aws5 – RESTful web service for converting plain/text from UTF-8 to WIN-1251 enc. Available via GitHub
repository [
        <xref ref-type="bibr" rid="ref41">37</xref>
        ].
aws6 – RESTful web service for automatic detection of title, author’s names, and page numbers for PDF files.
aws7 – RESTful web service for automatic keyword plain/text detection.
aws8 – RESTful web service for automatic sentence segmentation.
aws9 – RESTful web service for automatic word segmentation with lemmatization and Part-of-speech tagging.
aws10 – RESTful web service for automatic word segmentation.
      </p>
      <p>aws11 – RESTful web service for Compositional Language Pre-processing (CLP): term segmentation
(dividing a string of written language into multiple-word and one-word terms) with lemmatization and
Part-ofspeech tagging.</p>
      <p>aws12 – RESTful web service for automatic “stop words” filtering out. These are words that do not bear the
semantic load.</p>
      <p>aws13 – RESTful web service for automatic word lemmatization.</p>
      <p>
        aws14 – RESTful web service for syntactic parser SyntaxNet: Neural Models of Syntax: an open-source neural
network framework implemented in TensorFlow that provides a foundation for Natural Language Understanding
(NLU) systems [
        <xref ref-type="bibr" rid="ref42 ref43 ref44">38 – 40</xref>
        ].
      </p>
      <p>
        aws15 – RESTful web service for searching scientific publications in external bibliographic databases (an
intelligent agent for the automated search of scientific publications [41]). Google Scholar search implemented via
scholar.py [
        <xref ref-type="bibr" rid="ref45">42</xref>
        ] library.
      </p>
      <p>
        aws16 – RESTful web service for text indexing and annotating (for full-text search capability).
aws17 – MongoDB as a service (storing the originals of text documents and texts, ontological str uctures,
ontologies, processed texts in the form of JSON-documents, neural language vector models (NLVM) – word
embedding models [
        <xref ref-type="bibr" rid="ref46 ref47">43 – 44</xref>
        ]).
      </p>
      <p>
        aws18 – “Graph Editor” – web service (represented as Single Page Application – SPA) for text’s ontological
representation, for manipulating ontologies and ontological structures. “Graph Editor” is a part of “TODOS” [
        <xref ref-type="bibr" rid="ref48">45</xref>
        ] –
IT-platform formation transdisciplinary information environment.
      </p>
      <p>
        aws19 – “CONFOR” [
        <xref ref-type="bibr" rid="ref49">46</xref>
        ] – web service (represented as SPA) for intelligent data analysis. The main
functions of “CONFOR” are: revealing the regularities that characterize classes of objects which are represented as
sets of attribute values; using the revealed regularities for classification, diagnostics, and prediction.
      </p>
      <p>aws20 – “KONSPEKT” [47] – web service (represented as SPA) for syntactic and semantic analysis of natural
language texts.</p>
      <p>
        aws21 – RESTful web service for processing NLVM of large corpora or open data collections (ODC):
implemented via custom gensim [
        <xref ref-type="bibr" rid="ref50">48</xref>
        ] as a service server application. It is possible to [
        <xref ref-type="bibr" rid="ref51">49</xref>
        ]: calculate semantic
similarity between pair of terms (including multiple-word terms, one-word terms, words) within the chosen NLVM;
compute a list of nearest semantic associates for terms (including multiple-word terms, one-word terms, words)
within the chosen NLVM; find the center of lexical cluster for a set of terms (including multiple -word terms,
oneword terms, words) within the chosen NLVM; calculate semantic similarity between two sets of terms (including
multiple-word terms, one-word terms, words) within the chosen NLVM.
      </p>
      <p>aws22 – “Personal ontological knowledge base for researcher’s publications” web service [50] (represented as SPA).
aws23 – Web service (represented as SPA) for creating and filling out templates that will allow to generate an
incoming flow of documents coming from applicant of invention for industrial property [33].</p>
      <p>aws24 – additional external FLOSS (web services, libraries, utilities, etc.);</p>
      <p>The F set. Functional filling-up of the PRIS is represented by the following set of synthesized from the set of
AWS functions:</p>
      <p>F  AWS:C1 ,C2 ,C3 ,C4 ,C5 ,C6 ,C7 ,</p>
      <p>
        C1 – ontology engineering. The automated building of applied ontology in an arbitrary domain area (or
knowledge domain). The fundamental foundations of the implemented technology are described in the works [
        <xref ref-type="bibr" rid="ref7">50 – 55</xref>
        ]:
C1  aws1
aws3 ,aws5 ,aws6 ,aws8 ,aws9 ,aws11 ,aws12 ,aws14 ,aws16
aws20 ;
C2 – the research design of scientific publications in an arbitrary domain area (or knowledge domain) [33, 50]:
C2  aws1
      </p>
      <sec id="sec-8-1">
        <title>C3 – personalized ontological processing of scientific publications [33, 50]: C4 – the automated CLP for training and querying NLVM for large corpora or ODC [33]:</title>
        <p>C3  aws1</p>
      </sec>
      <sec id="sec-8-2">
        <title>C5 – the automated distributive and semantic analysis of large corpora or ODC [33]:</title>
      </sec>
      <sec id="sec-8-3">
        <title>C6 – the automatic syntactic parsing:</title>
        <p>C5  aws21 ,aws24;
C6  aws1</p>
        <p>aws3 ,aws8 ,aws14 ,aws20 ,aws24 ;</p>
        <p>
          C7 – the automated preparation of application documents for patenting inventions in Ukraine. The fundamental
foundations of the implemented technology are described in [
          <xref ref-type="bibr" rid="ref8">33, 56</xref>
          ]:
        </p>
        <p>C7  aws1</p>
        <p>aws3 ,aws21 ,aws23 ,aws24</p>
      </sec>
    </sec>
    <sec id="sec-9">
      <title>Conclusion</title>
      <p>The development of modern technologies increasingly covers the field of intellectual activity and, especially,
in the field of scientific research and development. The existing Current Research Information Systems oriented on
the following main types of services: access and reuse of scientific and academic information, methodologies, and
technologies; information search; targeted dissemination of information; messaging services; bridging of horizontal
and vertical relations between scientists; backup data storage and archival information.</p>
      <p>We propose the new class of Current Research Information Systems and related intelligent information
technologies. This class supports the main stages of the scientific research and development lifecycle, starting with
the semantic analysis of the information of arbitrary domain area and ending with the formation of constructive
features of innovative proposals. It was called – Research and Development Workstation Environment – the
comprehensive problem-oriented information systems for scientific research and development support. A distinctive
feature of such systems is the possibility of their problematic orientation to various types of scientific activities by
combining on a variety of functional services and adding new ones within the Cloud-integrated Environment. Taking
into account the objective factor of Ukrainian science state, we define the general principles of the RDWE design:
modular design; microservices-based architecture; cross-platform software (also multi-platform software or
platform-independent software); JSON/XML data model and REST architectural style (RESTful web services);
using free and open-source software; cloud computing; data storage based on the abstraction of data repository; data
repositories synchronization.</p>
      <p>The Research and Development Workstation Environment class system’s generalized information model is
represented in the article as a three-tuple composite web service that include: a set of atomic web services, each of
them can be designed and developed as a microservice or a desktop application, that allows them to be used as an
independent software separately; a set of functions, the functional filling-up of the Research and Development
Workstation Environment; a subset of atomic web services that are required to implement function of composite web
service. In accordance with the fundamental information model of the Research and Development Workstation
Environment systems, the Personal Research Information System information model was developed.</p>
      <p>The main results of our work are focused on enhancing the effectiveness of the scientist’s research and
development lifecycle in the arbitrary domain area. In the future, it would be interesting to apply to the educational
process the modern paradigm of Service-Oriented Learning implemented as Personal Learning Environments,
Virtual Learning Environments, Learning Management Systems, Education-as-a-Service models, and the new class
of E-learning systems – Cloud Learning Environments – using RDWE systems as a E-learning/education-oriented
environment.
Література</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Houssos N.</surname>
          </string-name>
          <year>2011</year>
          .
          <article-title>CRIS for research information management</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <source>ERGO - European Research Gateways Online</source>
          <year>2018</year>
          , viewed
          <issue>07</issue>
          <year>February 2018</year>
          , &lt;https://cordis.europa.eu/news/rcn/8259_en.html&gt;.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          euroCRIS - The
          <source>International Organization for Research Information</source>
          <year>2018</year>
          , viewed
          <issue>07</issue>
          <year>February 2018</year>
          , &lt;https://www.eurocris.org&gt;.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <source>Main features of CERIF: The Common European Research Information Format</source>
          <year>2018</year>
          , viewed
          <issue>07</issue>
          <year>February 2018</year>
          , &lt;https://www.eurocris.org/cerif/main-features-cerif&gt;.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <article-title>Modern scientific information systems</article-title>
          .
          <source>Prospects of use</source>
          <year>2001</year>
          , viewed
          <issue>07</issue>
          <year>February 2018</year>
          , &lt;http://derpi.tuwien.ac.at/~andrei/CRIS_DOC.htm&gt;.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Tan</surname>
            <given-names>W.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Zhou</surname>
            <given-names>M.</given-names>
          </string-name>
          <year>2013</year>
          . Business and
          <string-name>
            <given-names>Scientific</given-names>
            <surname>Workflows</surname>
          </string-name>
          :
          <string-name>
            <given-names>A Web</given-names>
            <surname>Service-Oriented Approach</surname>
          </string-name>
          (Vol.
          <volume>5</volume>
          ). John Wiley &amp; Sons.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          55.
          <string-name>
            <surname>Palagin</surname>
            <given-names>A.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petrenko</surname>
            <given-names>N.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Velichko</surname>
            <given-names>V.</given-names>
          </string-name>
          <string-name>
            <surname>Yu</surname>
          </string-name>
          .,
          <string-name>
            <surname>Malakhov</surname>
            <given-names>K.S.</given-names>
          </string-name>
          and
          <string-name>
            <given-names>Tikhonov</given-names>
            <surname>Yu</surname>
          </string-name>
          .
          <string-name>
            <surname>L.</surname>
          </string-name>
          <year>2012</year>
          .
          <article-title>To the problem of “The Instrumental complex for ontological engineering purpose” software system design. Problems in programming, N 2-3</article-title>
          . P.
          <volume>289</volume>
          -
          <fpage>298</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          56.
          <string-name>
            <surname>Palagin</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kurhaiev</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petrenko</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Semotiuk</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Velychko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marchenko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malakhov</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yakovlev</surname>
            ,
            <given-names>Yu.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kurzantseva</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sosnenko</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Samoliuk</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hryhoriev</surname>
          </string-name>
          . S.,
          <year>2017</year>
          .
          <article-title>Rozrobka elementiv tekhnolohii informatsiino-ontolohichnoi pidtrymky naukovo-tekhnichnoi tvorchosti</article-title>
          .
          <source>Project report 205.38</source>
          .17.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          1.
          <string-name>
            <surname>Houssos</surname>
            <given-names>N.</given-names>
          </string-name>
          <article-title>CRIS for research information management</article-title>
          . URL: http://hdl.handle.net/11366/303 (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          2. ERGO - European Research Gateways Online. URL: https://cordis.europa.eu/news/rcn/8259_en.
          <source>html (Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          3. euroCRIS - The International Organization for Research Information. URL: https://www.eurocris.
          <source>org (Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          4.
          <article-title>Main features of CERIF: The Common European Research Information Format</article-title>
          . URL: https://www.eurocris.org/cerif/main-features-cerif
          <source>(Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          5.
          <string-name>
            <surname>Лопатенко</surname>
            <given-names>А</given-names>
          </string-name>
          .С.
          <article-title>Современные научные информационные системы. Перспективы использования</article-title>
          . URL: http://derpi.tuwien.ac.at/~andrei/CRIS_DOC.
          <source>htm (дата звернення: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          6.
          <string-name>
            <surname>Wei</surname>
            <given-names>Tan</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>MengChu</given-names>
            <surname>Zhou</surname>
          </string-name>
          . Business and
          <string-name>
            <given-names>Scientific</given-names>
            <surname>Workflows</surname>
          </string-name>
          :
          <string-name>
            <given-names>A Web</given-names>
            <surname>Service-Oriented Approach</surname>
          </string-name>
          . New Jersey,
          <year>2013</year>
          . 264 p.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          8.
          <string-name>
            <surname>Lindgren</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rautamki</surname>
            <given-names>A</given-names>
          </string-name>
          .
          <article-title>Managing strategic aspects of research</article-title>
          .
          <source>Proceedings CRIS-2000</source>
          , Helsinki. URL: https://pdfs.semanticscholar.
          <source>org/ca88/763a60bf5adfa32aaa67bc284a842f4c2887.pdf (Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          9.
          <string-name>
            <surname>Dew</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leigh</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whyte</surname>
            <given-names>B. ADVISER II</given-names>
          </string-name>
          :
          <article-title>Theory and practice of finding and presenting RTD results</article-title>
          .
          <source>Proceedings CRIS-2000</source>
          , Helsinki. URL: ftp://ftp.cordis.lu/pub/cris2000/docs/dewBfulltext.pdf (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          10. CORDIS - Community Research and
          <article-title>Development Information Service</article-title>
          . URL: https://cordis.europa.eu/home_en.
          <source>html (Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          11. ResearchGate. URL: https://www.researchgate.net/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          12.
          <string-name>
            <surname>Helge</surname>
            <given-names>P.</given-names>
          </string-name>
          <article-title>A quick glance at business models of academic social networking services</article-title>
          . Hybrid Publishing Lab Notepad. URL: http://hybridpublishing.org/
          <year>2013</year>
          /01/a
          <article-title>-quick-glance-at-business-models-of-academic-social-networking-services/</article-title>
          (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          13. Academia.edu - Share research. URL: https://www.academia.edu/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          14.
          <string-name>
            <surname>Mendeley - Reference Management</surname>
          </string-name>
          Software &amp;
          <article-title>Researcher Network</article-title>
          . URL: https://www.mendeley.com/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          15.
          <string-name>
            <surname>Van den Eynden</surname>
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corti</surname>
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Woollard</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bishop</surname>
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horton</surname>
            <given-names>L</given-names>
          </string-name>
          .
          <article-title>Managing and sharing data: best practice for researchers</article-title>
          .
          <source>UK</source>
          ,
          <year>2011</year>
          . 40 p.
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          16.
          <string-name>
            <surname>Kothari</surname>
            <given-names>C.R.</given-names>
          </string-name>
          ,
          <source>Guarav Garg. Research Methodology: Methods and Techniques 3rd edition. New Delhi</source>
          ,
          <year>2014</year>
          . 449 p.
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          17.
          <string-name>
            <surname>Прокудин</surname>
            <given-names>Д</given-names>
          </string-name>
          .Е.
          <article-title>Проектирование и реализация комплексной информационной системы поддержки научных исследований. Технологии информационного общества в науке, образовании и культуре: сборник научных статей. Материалы научной конференции “Интернет и современное общество” IMS-2014 (</article-title>
          <string-name>
            <surname>Санкт-Петербург</surname>
          </string-name>
          19-20 ноября
          <year>2014</year>
          ). Санкт-Петербург,
          <year>2014</year>
          . С.
          <volume>31</volume>
          -
          <fpage>36</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          18. ORCID - Connecting Research and Researchers. URL: https://orcid.org/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          19. ResearcherID. URL: http://www.researcherid.com/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          20.
          <article-title>OpenID Foundation website</article-title>
          . URL: https://openid.net/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          21.
          <string-name>
            <surname>Vestdam</surname>
            <given-names>T.</given-names>
          </string-name>
          <article-title>The future of CRIS systems - an interplay with VIVO</article-title>
          .
          <source>4th Annual VIVO Conference (St Louis, Aug 14-16</source>
          ,
          <year>2013</year>
          ). URL: http://hdl.handle.net/11366/334 (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          22.
          <string-name>
            <surname>Wiederhold L. Cooperative</surname>
          </string-name>
          <article-title>Structures for the Collection of Internet Resources on and from the Middle East</article-title>
          . URL: http://www.bibliothek.unihalle.de/text/vortraege/venedig.htm (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          24.
          <string-name>
            <surname>Nabielsky</surname>
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Skelton</surname>
            <given-names>A.P. A Virtual</given-names>
          </string-name>
          <string-name>
            <surname>Terminal</surname>
          </string-name>
          <article-title>Management Model</article-title>
          . URL: https://www.rfc-editor.
          <source>org/pdfrfc/rfc782.txt.pdf (Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          25. What are microservices? URL: http://microservices.io/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          26.
          <string-name>
            <surname>Dvorkin E. Seven</surname>
          </string-name>
          micro
          <article-title>-services architecture advantages</article-title>
          .
          <source>Art of Software Engineering</source>
          . URL: http://eugenedvorkin.com/seven-micro
          <string-name>
            <surname>-</surname>
          </string-name>
          servicesarchitecture-advantages/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          27.
          <string-name>
            <surname>Node</surname>
          </string-name>
          .js
          <article-title>- JavaScript runtime built on Chrome's V8 JavaScript engine</article-title>
          . URL: https://nodejs.org (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          28.
          <string-name>
            <surname>Fielding</surname>
            <given-names>R.T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taylor R</surname>
          </string-name>
          .N.
          <article-title>Architectural styles and the design of network-based software architectures</article-title>
          .
          <source>Doctoral dissertation</source>
          : University of California, Irvine,
          <year>2000</year>
          Vol.
          <volume>7</volume>
          . URL: https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.
          <source>pdf (Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          29.
          <string-name>
            <surname>Etzkorn L.H. Introduction</surname>
            to Middleware: Web Services,
            <given-names>Object</given-names>
          </string-name>
          <string-name>
            <surname>Components</surname>
            , and
            <given-names>Cloud</given-names>
          </string-name>
          <string-name>
            <surname>Computing</surname>
          </string-name>
          . CRC Press,
          <year>2017</year>
          . 662 p.
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          30.
          <string-name>
            <surname>Bhowmik</surname>
            <given-names>S. Cloud</given-names>
          </string-name>
          <string-name>
            <surname>Computing</surname>
          </string-name>
          . Cambridge University Press,
          <year>2017</year>
          . 462 p.
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          31.
          <article-title>National Institute of Standards and Technology</article-title>
          . URL: https://www.nist.gov/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          34.
          <string-name>
            <surname>Atomic</surname>
          </string-name>
          <article-title>Web Service for converting PDF files to plain/text</article-title>
          . URL: https://github.com/malakhovks/pdf-extract-api
          <source>(Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          35.
          <string-name>
            <surname>Atomic</surname>
          </string-name>
          <article-title>Web Service for converting DOC/DOCX files to plain/text</article-title>
          . URL: https://github.com/malakhovks/doc-docx
          <article-title>-extract-api (Last accessed</article-title>
          :
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref40">
        <mixed-citation>
          36.
          <string-name>
            <surname>Atomic</surname>
          </string-name>
          <article-title>Web Service for automatic text summarization</article-title>
          . URL: https://github.com/malakhovks/text-summarization-api
          <source>(Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref41">
        <mixed-citation>
          37.
          <string-name>
            <surname>Atomic</surname>
          </string-name>
          <article-title>Web Service for converting text from UTF-8 to WIN-1251</article-title>
          . URL: https://github.com/malakhovks/utf8-to-win1251-
          <source>api (Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref42">
        <mixed-citation>
          38.
          <string-name>
            <surname>Petrov S. Announcing</surname>
            <given-names>SyntaxNet</given-names>
          </string-name>
          :
          <article-title>The World's Most Accurate Parser Goes Open Source</article-title>
          . Google Research Blog. URL: https://research.googleblog.com/
          <year>2016</year>
          /05/announcing-syntaxnet
          <article-title>-worlds-most</article-title>
          .
          <source>html (Last accessed: 07.02</source>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref43">
        <mixed-citation>
          39.
          <source>SyntaxNet: Neural Models of Syntax</source>
          . URL: https://github.com/tensorflow/models/tree/master/research/syntaxnet (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref44">
        <mixed-citation>
          40.
          <article-title>TensorFlow - An open-source machine learning framework for everyone</article-title>
          . URL: https://www.tensorflow.org/ (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref45">
        <mixed-citation>
          42. ckreibich/scholar.py:
          <article-title>A parser for Google Scholar, written in Python</article-title>
          . URL: https://github.com/ckreibich/scholar.py (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref46">
        <mixed-citation>
          43.
          <string-name>
            <surname>Mikolov</surname>
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chen</surname>
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corrado</surname>
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dean</surname>
            <given-names>J</given-names>
          </string-name>
          .
          <article-title>Efficient Estimation of Word Representations in Vector Space</article-title>
          .
          <source>arXiv preprint arXiv:1301</source>
          .3781. URL: https://arxiv.org/abs/1301.3781 (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref47">
        <mixed-citation>
          44.
          <string-name>
            <surname>Bojanowski</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grave</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Joulin</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mikolov</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <article-title>Enriching word vectors with subword information</article-title>
          .
          <source>arXiv preprint arXiv:1607</source>
          .04606. URL: https://arxiv.org/abs/1607.04606 (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref48">
        <mixed-citation>
          45.
          <string-name>
            <surname>Величко</surname>
            <given-names>В. Ю.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Малахов</surname>
            <given-names>К</given-names>
          </string-name>
          . С.,
          <string-name>
            <surname>Семенков</surname>
            <given-names>В</given-names>
          </string-name>
          . В.,
          <string-name>
            <surname>Стрижак</surname>
          </string-name>
          , А. Е.
          <article-title>Комплексные инструментальные средства инженерии онтологий</article-title>
          .
          <source>Information Models and Analyses</source>
          .
          <year>2014</year>
          . № 4. С.
          <volume>336</volume>
          -
          <fpage>361</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref49">
        <mixed-citation>
          46.
          <string-name>
            <surname>Gladun</surname>
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Velychko</surname>
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ivaskiv</surname>
            <given-names>Y. Selfstructurized</given-names>
          </string-name>
          <string-name>
            <surname>Systems</surname>
          </string-name>
          . //
          <source>International Journal "Information Theories &amp; Applications"</source>
          .
          <source>FOI ITHEA</source>
          , Sofia.
          <year>2008</year>
          . Vol.
          <volume>15</volume>
          . N 1. P. 5-
          <fpage>13</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref50">
        <mixed-citation>
          48.
          <article-title>RaRe-Technologies/gensim: Topic Modelling for Humans</article-title>
          . URL: https://github.com/RaRe-Technologies/gensim (Last accessed:
          <volume>07</volume>
          .
          <fpage>02</fpage>
          .
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref51">
        <mixed-citation>
          49.
          <string-name>
            <surname>Kutuzov</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuzmenko</surname>
            <given-names>E.</given-names>
          </string-name>
          (
          <year>2017</year>
          )
          <article-title>WebVectors: A Toolkit for Building Web Interfaces for Vector Semantic Models</article-title>
          . In: Ignatov D. et al. (
          <article-title>eds) Analysis of Images, Social Networks and Texts</article-title>
          .
          <source>AIST 2016. Communications in Computer and Information Science</source>
          , vol
          <volume>661</volume>
          . Springer, Cham.
        </mixed-citation>
      </ref>
      <ref id="ref52">
        <mixed-citation>
          <string-name>
            <given-names>Oleksandr</given-names>
            <surname>Palagin</surname>
          </string-name>
          ,
          <source>Doctor of Sciences, Academician of National Academy of Sciences of Ukraine, Deputy director of Glushkov Institute of Cybernetics</source>
          , head of department 205 at Glushkov Institute of Cybernetics, 290 Ukrainian publications, 45 International publications, H-index: Google Scholar -
          <volume>15</volume>
          , Scopus -
          <volume>3</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref53">
        <mixed-citation>http://orcid.org/0000-0003-3223-1391.</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>