Difference between revisions of "Web Dictionary Maintenance"
| Line 235: | Line 235: | ||
==Example of Iteraction== |
==Example of Iteraction== |
||
[[File:SequenceDiagramWebDictionary.jpg|thumb|500px|right|Example Sequence Diagram]] |
[[File:SequenceDiagramWebDictionary.jpg|thumb|500px|right|Example Sequence Diagram]] |
||
| + | ===1. Choosing an official dictionary and importing it=== |
||
| + | ===2. Loading the dictionary file=== |
||
| − | The general flow occurs as follows: |
||
| + | ===3. Verifying if the lemmas already exists=== |
||
| − | # The user chooses an available dictionary in the Git repository and starts a new branch from some version (or starts a new empty dictionary); |
||
| + | |||
| − | # The XML of the chosen dictionary will be processed and saved in a temporary database, where it will be easier to perform the necessary crosses and make the modifications; |
||
| + | ===4. Creating the new lemma=== |
||
| − | # Through the GUI, the user will make their modifications in the dictionary and the changes will be temporarily saved in the database. |
||
| + | |||
| − | # When finalizing your modifications, the user can commit. A new XML will be generated from the database with the modifications made by the user. From that point on, that user's branch will be available for other users to use. |
||
| + | ===5. Request to merge=== |
||
| − | # When deemed convenient, the user can merge request with the official branch (or a branch of another user), which will be analyzed by the people in charge of the dictionary. |
||
| + | |||
| − | # The environment will make use of the GitLab platform (or similar tool) as an administrative tool and version control of dictionaries. |
||
| + | ===6. Official dictionary keeper judges the merge request=== |
||
| − | # When initiating a modification in a dictionary, the user will select one of the versions available in the Git repository and the XML of the selected branch will be cloned and adapted to be saved in a database (where it will be more efficient to make the necessary crosses). The user will then be free to make any changes he deems necessary. At the end of your contribution, the environment will prompt you to create a new branch with the user-modified XML, and then you can merge another branch where the team responsible for the dictionary can accept or deny the change. |
||
| + | |||
| + | ===7. Feedback=== |
||
==First Experiments== |
==First Experiments== |
||
Revision as of 20:52, 25 March 2019
Translate to PT-BR with Google Tradução
Introduction
Apertium over the years still has deficiencies so that lay people can contribute to increase the base of words in dictionaries, even with simple contributions. Collaboration is the key to developing a tool that serves a huge range of users throughout the world. We believe that it is possible to engage more users and thus give greater impact to the tool within the communities where there is involvement. We will deal in this document with requirements on non-functional and technical objectives regarding the tool proposal.
- Original Ideias
- http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code
- http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code/Easy_dictionary_maintenance
- Original GSOC2019 Application
- http://wiki.apertium.org/wiki/User:Alessiojr/Easy_dictionary_-_Application-GSOC2019
- Studant Information
- Student: Vinícius Silva Nogueira
- Unofficial Mentor: Alessio Miranda Junior
- Telegram/Whatsapp: Alessio: +55 (31) 9.8888-7770
- E-mail: alessio@cefetmg.br or viniciussnogueira13@gmail.com
- IRC: AlessioJr
- GTalk: alessiojunin@gmail.com
Description
Abstract:
The dictionaries complexity and size makes its modification extremely hard and time-consuming, and, along with the need for programming knowledge, keeps away potential contributors. A tool that facilitates the work of dictionaries developers, eliminate computer knowledge (XML, Git, etc) and that allows collaboration between members of the community is of extreme necessity because, with the removal of these barriers, a larger group of people will have the necessary requirements to participate in the development of dictionaries, thus increasing the translation capacity of Apertium.
Even with several tools that help the way you manage and create dictionaries, Apertium is far from the normal users, who have a huge contribution potential. Or even create a simple way to create contributions to recurring users with advanced knowledge. Although it is a bold plan, and there are several possible and desirable requirements, we will describe some basic premises for this step and that must be respected and aligned with the apertium developer community.
Definitions
- Lay users do not need to know Apertium's internal structure.
- Intermediate users need to have a knowledge of dictionary management methodology.
- Advanced users are those who know the structure of Apertium.
- Communities are user groups that merge characteristics to the database extension of a dictionary of a specific language.
- Official dictionaries are dictionaries managed and with seal of the apertium community.
- Unofficial dictionaries are dictionaries run by an independent community.
- Test dictionaries are deprived of users to test their contributions.
Objectives:
- The major goal of the project is to develop a web tool to facilitate the management of the Apertium (XML's) database of integrators for novice and advanced users.
- New communities of contributions should be able to organize independently of a central command. The command exists but will be distributed.
- Lay users who feel motivated to contribute, should have an interface that promotes ease in contributing even with limited possibilities.
- The development of dictionaries should be collaborative and distributed. Each dictionary should have a management community, but a user may have the freedom to disagree and create a new version maintaining a history of the author.
- Any tool should maintain the traditional Apertium structure and not be interoperable between existing tools.
- There must be a methodology for communities to maintain the quality of their dictionaries. Although they are distributed the goal is to create a unified and mature dictionary.
Technical Objectives:
- Develop, initially, monolingual dictionaries but keeping the particular format of each file.
- Minimize the direct manipulation of XML files, providing features that reduce this need.
- Making use of GitLab as an administrative and control tool.
Git, GitLab and Apertium
As the Apertium files are textual, we had the idea of seeking productivity and using existing and consolidated tools in the world. The proposal is to build a friendly web interface for lay users, but use git's own Back-End as version control and to make dictionary management GitLab as an administrative tool that already guarantees incredible power for remote collaboration.
To demonstrate this relationship we will highlight some concepts of Git. Over time there may be several TimeLines:
- The Official Branch (Master) has the official version of the apertium managed by official developers or maintainers.
- Users have the power to create new Branches and develop unofficial dictionaries in parallel, creating communities that may from time to time suggest modifications to Brach Master.
- These requests can be accepted or rejected by maintainers, and this format is recursive and other developers can create unofficial copies of unofficial ones.
- Integration requests will use the Merge Request concepts present in tools such as GitLab that will be the BackEnd for advanced users.
Application-GSOC2019
Abstract:
The idea is to develop the Web tool so that lay users contribute to dictionaries and use Git management with GitLab to manage these changes. * The focus will be on monolingual dictionaries and bilingual direct relationships. * Use the Git methodology and propose a guideline or flow for collaborative dictionary management. * Do not change the current XML format of dictionaries.
Why is it you are interested in machine translation?
During the graduation course, Professor Aléssio demonstrated the need and opportunity to contribute with open source projects. He introduced me to Apertium and in my final graduation work I started reading and talking about it. We started discussing techniques for managing collaboration with the community and currently do not have as much knowledge about machine translation machines but I have experience in developing applications and web using collaboration with Git and GitLab.
Why are they interested in the Apertium project?
I’ve .
Which of the published tasks are you interested in?
Easy dictionary maintenance.
Why should Google and Apertium sponsor it?
I .
How and who will it benefit in society?
I .
What do you plan to do?
We.
Development Paradigm: MVC Paradigm
Program Language: Java, JavaScript
Persistence: XML (Apertium XML Files)
Framworks: Angular
Stages/Milestones
| Week | Stage | Description |
|---|---|---|
| 1, 2 | -- | --. |
| 2, 3 | -- | |
| Prototype | Milestone 1 | -- |
| 5, 6 | -- | --. |
| 7 | -- | --. |
| 8 | -- | --. |
| Prototype | Milestone 2 | -- |
| 9 | -- | --. |
| 10 | -- | --. |
| 11 | Pré-Release | -- |
| Prototype | -- | |
| 12 | Makeup | -- |
| Final Release |
Presentation
My name is Vinicius, a Brazilian Student at Federal Center for Technological Education of Minas Gerais - Brazil.
Resume of Skills
Apertium Knowledge:
* Study to develop a collaborative tool for apertium. * A study of actual Apertium process about creating a language pair by the user point of view. * Analysis of the characteristics of the 2010 project of Aléssio and adaptation to current times.
Academic Skills:
* Graduating in Computer Engineering- Federal Center for Technological Education of Minas Gerais – Brazil
Professional Skills:
* Language developer: C, Java, JavaScript, PHP, Phyton, PL/SQL.
Projects for Summer:
* No professional activities planned. * Planning to work in GSOC
Project
Why?
- The dictionaries complexity and size makes its modification extremely hard and time-consuming, and, along with the need for programming knowledge, keeps potential contributors away. A tool that facilitates the work of dictionaries developers, eliminate the need of computer knowledge (XML, Git, etc) and that allows collaboration between members of the community is of extreme necessity because, with the removal of these barriers, a larger group of people will have the necessary requirements to participate in the development of dictionaries, thus increasing the translation capacity of Apertium.
How can use?
- --.
- --.
- --.
- --.
What its the plan?
- We are planning to create a web GUI that allows the user to develop the basic tasks of dictionaries and translation pairs manipulation in an easy and practical way.
- We will use Git as an administrative and control tool, allowing the user to contribute to the work of other community members or start your own project.
Components ans Technologies
- Actors
- Lay User
- Dictionary Admin
- UserBrowser
- WebInterface with AngularJS - GUI to easily manipulate the dictionary XML file.
- Web Dicionary Maintence (APP)
- WebAPI -
- Temporary Database - Temporary database in which the XML file will be loaded with the crosses made.
- JavaGit Connector -
- WebDictionary Controller -
- Git -
- GitRepository -
- GitLab -
- GitHub -
How it Works?
We will develop a WebInterface to LayUser add words or sugest modifiations.
We are planning to use Git as an administrative and version control tool.
- All dictionaries releases will be in a single repository and available to any member of the community to continue the work.
- Each user will have your own branch to work on.
- The users will be able to make merge requests with the official branch.
- At first, we will use GitLab (or similar tool) to manage this merges requests. The team who maintain each dictionary will judge if the modifications are valid or not.
