OpenLLM-France/wikimedia huggingface dataset:
# Final Fantasy/Classes/Black Mage

Black Mages are wielders of the destructive black magic. They use the elements of the world, poison, and mental attacks to destroy their foes. The nature of the spells cast by the Black Mage often causes observers to wonder if the Black Mage is not just as evil as the creatures that he fights.
Black Mages have no religious restrictions in their choice of weaponry, but often have no skill in using anything more complicated than a staff or dagger.
Expert Final Fantasy players question the value of the Black Mage/Wizard. The Black Mage can be useful early on, but later in the game become liabilities due to their physical weakness. Also, almost all useful Black Magic spells are available to the Red Wizard.
Black Mages upgrade to Black Wizards.

## Initial Statistics

The Black Mage is the most specialized of all of the classes when it comes to statistics. None are more Intelligent than the Black Mage, but at the same time none have less Strength or Vitality. The Black Mage does have above-average scores in Agility and Luck, however.
| Strength | 1 |
| Agility | 10 |
| Intelligence | 20 |
| Vitality | 1 |
| Luck | 10 |

## Spells

Black Mages cast only Black Magic spells.
| Character Level | Level 1 | Level 2 | Level 3 | Level 4 | Level 5 | Level 6 | Level 7 | Level 8 |
| Lvl 1 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Lvl 2 | 3 | 1 | 0 | 0 | 0 | 0 | 0 | 0 |
| Lvl 3 | 3 | 2 | 0 | 0 | 0 | 0 | 0 | 0 |
# Final Fantasy/Classes/Black Wizard

The Black Wizard is an upgraded Black Mage. Black Wizards have full access to every Black Magic spell known to man, including the devastating Nuke.
# Final Fantasy/Characters/Prince of Elfland

The Prince of Elfland rules over the realm of Elfland. He was entrusted with the safekeeping of the Mystic Key by the rulers of Coneria when they sealed their Treasury to protect its contents from the Four Fiends 400 years ago.
He was cursed by Astos five years before the Light Warriors began their quest. The curse took the form of a deep sleep from which the Prince cannot awaken until cured with the Herb, which only Matoya is able to prepare.
# Final Fantasy/Classes

Final Fantasy uses a class system in which the player chooses the classes of the four heroes at the beginning of the game. These classes cannot be changed after this (except for promoting them by completing the Castle of Ordeal quest). There are six classes to choose from.
| Original Class | Upgraded Class |
| Fighter | Knight |
| Thief | Ninja |
| Black Belt | Master |
| Red Mage | Red Wizard |
| White Mage | White Wizard |
| Black Mage | Black Wizard |
# GNU Health/Administration
## About the Administration Section

At the lower end of the main navigation you will find the Administration section. This is the area where system administrators configure users (and their access rights), data structures (like models and fields), modules, elements of the user interface, or languages.
While the Health → Configuration section is specific to GNU Health, the Administration section is a basic part of Tryton. And while the Configuration section will be managed by medical or administrative staff of a health institution, the Administration section is under the control of IT staff.

## Overview

The Administration sections consists of the following sub-sections:
* User Interface
* Models
* Sequences
* Scheduler
* Localization
* Modules
* Users
* Countries
* WebDAV
Please refer to the following chapters of this book for details about these sub-sections.
← Installation · User Interface →
# GNU Health/Code of Conduct
## The GNU Health Code of Conduct

GNU Health is, first and foremost, a social project to bring freedom and equity in health care around the World. GNU Health involves much more than just technology. We strive to generate a friendly, welcoming and positive environment around the GNU Health community.
We expect everyone involved with the GNU Health project to follow this Code of Conduct. This not only includes developers and contributors to GNU Health but also anyone posting to GNU Health mailing lists or using the GNU Health Forums or chatting on GNU Health IRC channels, wiki, web site, public meeting, or private correspondence, or otherwise interacting with the GNU Health community. We will remove any and all access to GNU Health resources or privileges for whatever period it deems fit, up to and including a permanent ban where it rules that a transgression has happened.
* Be respectful to other members, as well as people outside or new to the community. Personal attacks, hate speech, trolling, arrogance, baiting, spamming, and discrimination on the basis of such things as gender, race, and sexuality, will not be tolerated.
* Avoid foul or abusive language: remember that cultural standards differ, and that what may seem to you to be a very mild statement can be deeply shocking to another.
* Be mindful : Our actions directly affect others, including colleagues and the public, and reflect on GNU Health work as a whole. Please keep it in mind when posting in the mailing list or chatting in the IRC or other communication media.
* Be grateful for the effort, time and talent of others, keeping in mind that often times the labor was completed simply for the good of the community. Be attentive in your communications, whether in person or online, and tactful when approaching differing views.
* Differing views are a strength, and they should be resolved constructively, always with an eye toward finding common ground. Try to pacify any disruptive situations as early as possible to prevent conflicts from escalating.
* Be concise : Most of us are very busy, and certainly don't appreciate never-ending, reiterative or out-of-topic threads. Please remain focused, clear, concise, and on-topic when creating or responding a thread.
* Avoid heated arguments, since they have a way of dragging in bystanders and mutating until the original point is lost. Keep focus and provide solid arguments. Never descend to the personal level.
* Developers: If contested, back out your changes first, then argue your case. Objections are hardly likely to be raised for trivial reasons, and commits can always be re-applied. Before committing code, share your ideas or patches. Asking for approval on any change is never a bad thing, and certainly courteous.
* Be positive : Positive attitude at personal level generates positive communities. Positivity builds motivation and allows to find solutions instead of living on problems. It’s the perfect ingredient for a successful, happy, optimistic and healthy community.
The GNU Health Code of Conduct is inspired in the FSF LibrePlanet and FreeBSD Code of Conduct.
# GNU Health/Book of Life

* This section applies to version 3.4 of GNU Health.

## Book of life

Our health is much more than just cold medical records. Most of the time, our health is the result of many events related to the environment, decisions we make, and interactions with many actors, that shape our life as individuals.

### Pages of Life

GNU Health command : POL
GNU Health has developed a way to record the relevant events on a person life. These events are not just medical, but also demographical, biographical and social. Each of those relevant events make a Page of Life of the individual.
Integration with GNU Health HMIS node: From the Hospital Management System Node (HMIS) of GNU Health, processes such as encounters, prescriptions, lab and diagnostic imaging are mapped to the book of life of the person.
In addition, the page of life allows the person to be in charge of their health information. The person will be able to read and post relevant information to be part of their Book of Life.
Components of the page of life: Currently the main page types are
* Demographical
* Biographical
* Medical
* Social
In addition, the medical and social categories have their context, to know:
Medical page contexts: Health condition, encounter, procedure, immunization, prescription, surgery, hospitalization, lab, Dx Imaging, genetics, family history, birth and death, among others.
Genetics: If the medical context is genetics, three additional fields will be shown: Gene, Natural variant, Phenotype
Social page contexts: Equity / Social gradient, stress, social exclusion, working conditions, education, physical environment, unemployment, social support, food, addiction, transport, health services, family functionality, family violence, bullying, war.

#### Page of Life link in the GNU Health Federation

Each page of life is unique. The GNU Health federation package includes the Page of Life model in the Federation. Any newly created page of life, and their modifications, can be then be shared across the federation Health Information System.
More information about the GNU Health Federation
# GNU Health/Access Management
## Access Management Overview

Like in many other IT systems, access to data and functions in GNU Health is controlled through groups (also known as roles). A group is a set of access rights. By assigning a user (also known as account or login) to a group, this user gains all rights of this group.

## Groups

To create, edit, or delete groups, please go to the Administration → Users → Groups section. Create a new group or double click an existing group to open the Groups form. All data in this form is divided into two tabs:

### Members Tab

The Members tab lists all users that have been assigned to this group. You can add users to the group here, or you can double click on a user to see this users details.
It is a safe practice to define all access rights of a group first and add users to the group later.

### Access Permissions Tab

The Access Permissions tab defines the access rights of a group. There are four types of rights that can be granted to a group:
* Access to a certain model: This allows to grant the right to read, write, create and/or delete records of a certain record type (or model as it is called in GNU Health).
* Access to a certain field: This allows to grant the right to read, write, create and/or delete data in certain field. While field access is not as commonly used as model access, this option allows you to fine tune your access permission and to protect sensitive data.
* Access to a certain menu item: This allows to show or hide sections in the main navigation. It is a good practice to hide sections where a group should not or cannot edit data to simplify the user interface.
* Access to a certain rule

## Users

To create, edit, or delete users, please go to the Administration → Users → Users section. Create a new user or double click an existing user to open the Users form.
Every user needs a Name (which is a descriptive name, not the user name for logging into the system) and a Status (which is active or not active and defines if a user can log into the system at all).
All other data in this form is divided into four tabs:

### User Tab

The User tab contains the very basic information about a user:
* Login: This is the user name for logging into the system and cannot be empty. It must be unique, that is to say that you can not have to users with identical logins.
* Password: This is the password for logging into the system. When entering a password you can check the checkbox on the right hand side of the Password field to see what you are entering.
* Email: If you enter a user's email address here, clicking on the globe icon on the right hand side of the Email field opens a new mail in your email client.

### Access Permissions Tab

In the Access Permissions tab a user can be assigned to one or more groups. Please be aware that not assigning groups here will lead to users who can log into the system but not do anything within the system.

### Preferences Tab

In the Preferences tab you can set the preferred language of a user.
← Stock Management · Socioeconomics →
# GNU Health/Calendars

A calendar has a name and an owner. The owner is a party specified as a person identified as a Health Professional, who has a profile as an Internal User.
# GNU Health/Community Pages

The following are links to individuals and communities related to GNU Health.
| Community | Link | Comments |
| Debian | | |
| openSUSE | https://en.opensuse.org/GNUHealth_on_openSUSE | Package-based one-click-install |
| user group Deutsch | https://hagenbichler.at/usergroup.html | info and reports in German |
# GNU Health/Analytic Accounting

← Financial Accounting · Products and Services Management →
# Backups

Refer to the GNU Health Control Center for more information
# GNU Health/Command Line

* This section applies to version 3.4 of GNU Health.

## Description

Since GNU Health 3.4, the HMIS client allows to use most of the functionality from the command line, without the need of the menu. It's much faster and direct than the previous menu-based client. Of course, the menu is still available.
Most commands accept arguments, so the user can go directly to one specific instance of the resource. For example
PAT : list all the people registered on the system
PAT ESPGNU777ORG : takes directly to the patient with federation account "ESPGNU777ORG"

## Accessing the command line

The command line can be accessed by clicking on the Command Line box (either at the top or bottom left of the client).
Clicking SHIFT + Z will put the focus on the Command Line Interface section.
Main GNU Health Commands :
| Command | Description |
| CMD | GNU Health Commands |
| PPL | Demographics |
| PAT | Patients |
| SYSINFO | Technical information for client and server |
| LAB | Lab Test Results |
| FEDQ | Federation objects queue |
| MED | Patient Medicaments |
| APP | Appointments |
| SES | Socioeconomics and Family Functionality Assessment |
| DU | Domiciliary Units |
| HP | Health Professionals |
| RX | Prescription Orders |
| EVL | Patient Evaluations |
| ECG | Electrocardiograms |
| RCRI | Revised Cardiac Risk Index |
| DX | Health Conditions |
| POL | Pages of Life |
| GEN | Personal Genetic Info |
| NEO | Newborn / Neonatal Information |
| OBS | Obstetric histories |
| SRV | Patient Health Services |
| SUR | Surgeries |
| MI | Medical Imaging Results |
| INV | Invoices |
| PRD | Products |
| CMD | GNU Health Commands |
| GDIS | Disease Genes |
| VAR | Natural variant phenotypes |
| VARP | Natural variant phenotypes |
| PDIS | Protein related diseases |
← Configuration · Patient Management →
# Ido/Prepositions

Preposition in Ido:
In = En
Into = Ad-en
After (in time) = Pos
After (behind) = Dop
On = Sur
Under = Sub
At (for someone's place/house) = Che
For = por
By = per
During = dum
Since = depos
To = A / Ad
Until = Til
Around = Cirkum
# Ido/Questions

To form questions that elicit yes/no reponses, place the particle "ka" or "kad" at the beginning of a sentence.
* Ka Sean iris a la skolo? Did Sean go to school?
* Kad el perdis la pekunio? Did she lose the money?
Simple questions may be formed by placing "Ka" in front of a noun without a verb. Ka Michelle? can mean "Is it Michelle?" or "Do you mean Michelle?", depending on the context.
If there is a word like who, what, where, etc., ka/kad is not used:
* Ube vu habitas? Where do you live?
* Quo es filozofio? What is philosophy?
* Quon vu timas? What do you fear?
* Qua es la prezidanto? Who is the president?
* Quante vu evas? How old are you?
# Ido/Verbs

All verbs in Ido are regular and have no exceptions.
The infinitive ends in -ar, the present tense in -as, the past tense in -is, the future tense in -os, the conditional tense in -us.
* Havar - to have
* Me havas - I have
* Ni havas - We have
* Me havis - I had
* Me havos - I will have
* Me havus - I should have
# Illustrated Guide to the world of Spira (FFX and FFX-2)/Culture
## Cultural aspects

From Wikipedia: Many elements of Final Fantasy X are drawn from Japanese culture and folklore. The names of most of the main cast are drawn from either Okinawan or Ainu words ("Yuna" meaning "blossom" in the former and "Wakka" "water" in the latter).. The world of Spira itself is ..modeled on southeast Asia, most notably with respect to its vegetation, topography, and architecture.

### Religion

The Teachings of Yevon—said to have been left by Yevon to his daughter, Lady Yunalesca—were implemented by Bevelle to maintain order through giving the people hope that Spira may someday be free of Sin should they atone for their "sins." Until Yuna exposed their lies, the Church of Yevon taught that machina was forbidden, that Sin was a result of humanity's pride and use of machina in the first place, and that Sin could only be vanquished when humanity had attained purity and been cleansed of its past sins. Until then, it was said that only the ritual known as "the Final Summoning" would provide brief reprieves from Sin's terror (called "Calms").

### Mythology

Like many of the precedent Final Fantasy games, the story lines of the role-playing games Final Fantasy X and Final Fantasy X-2 borrow ideas and names from ancient mythological figures and from past and present cultures such as Indian, Roman, Greek and Arabian, but the two games also have their own distinct mythology. The concepts of magic, spiritual energy, the power of memories, and the spirituality of the people are heavily intertwined, and their effects manifest in a number of situations, including sporting events, religious practices, the technology used by Spirans and even in some of the native wildlife of the planet.

### Hymn of the Fayth

The Hymn of the Fayth is a song composed by Japanese composer Nobuo Uematsu for Final Fantasy X. In the game, the Hymn serves as a transitional song and an indicator of religious importance or solemnity, though its lyrics don't appear to have any meaning to the game's characters. In the real world, the lyrics of the song require some deciphering to find their true meaning.

### Entertainment

Blitzball is the primary form of entertainment in Spira, a combination of football (also called "soccer" in some countries) and water polo. It is loved by almost everyone on Spira because it gives them something to think about other than Sin. The Yevon Cup and one Tournament is held every year.
Sphere Break is another popular game that sprung up in Spira after the beginning of the Eternal Calm. Unlike Blitzball, this game challenges the players' logical and mathematical abilities as well as their ability to concentrate under time pressure.
# Georgia Water/Statewide Plan/References

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Chapter 6. Statewide Plan

### References

* Caldwell, Nap, "The Process for Developing the Initial Edition of Georgia's Comprehensive Statewide Water Management Plan", in: Proceedings of the 2005 Georgia Water Resources Conference, held April 25-27, 2005, Athens, Georgia, pp. 29-30.
* O.C.G.A. Section 12.5.22, Comprehensive Statewide Water Management Planning Act
* Resolution 142, Final Report of the Joint Comprehensive Water Plan Study Committee, August, 2002
# Georgia Water/Statewide Plan/Timeline

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
* October 20, 2003 - Governor Sonny Perdue issued an Executive Order creating the Georgia Water Resources Council
* January 2004 - Georgia Water Resources Council submits recommendations to Georgia General Assembly.
* May 13, 2004 - Comprehensive State-wide Water Management Planning Act signed signed by Governor Sonny Perdue
* Mar. 02, 2005 - Georgia Water Council first meeting, DNR board room . . (summary)
* June 07, 2005 - Georgia Water Council second meeting, ARC Center, Atlanta . . (summary) . . :(Couch - the Planning Process). . . (Kundell presentation)
* Oct. 12, 2005 - Meeting of Water Conservation TAC in Atlanta, GA (agenda)
* Oct. 17, 2005 - Georgia Water Council meeting, ARC Center, Atlanta . . (agenda) . . :(Couch - Coastal Georgia Sound Science Initiative)
* Nov. 15, 2005 - Meeting of Water Conservation TAC in Tifton, GA
* Dec. 01, 2005 - Georgia Water Council meeting in DCA Board Room, Atlanta . . (agenda)
* July 01, 2007 - Due date for Georgia EPD to present the first statewide plan to the Georgia Water Council
# Georgia Water/Statewide Plan

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Chapter 6. Statewide Plan
    Georgia's Comprehensive Statewide Water Resources Management Plan
    Contributors
6.1. Introduction
   * Background
   * State Planning Act (HB 237 in 2004)
   * Georgia Water Council
6.2. Vision and Goals
6.3. Strategy for Developing the Statewide Plan
   * Overview of the Planning Process
   * Draft outline of the Statewide Water Plan
   * Part 1. State Water Policy - Review and New Tools (by July 2007)
   * Part 2. Framework for Regional Water Resources Plans (by July 2007)
   * Part 3. Regional Water Resources Plans (2008 onward)
6.4. Public Participation
   * Advisory Committees (appointed)
   * Other public participation
6.5. Budget
6.6. Timeline
6.7. References
# Georgia Water/Statewide Plan/Vision

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Vision, Goals and Objectives for Georgia's Statewide Water Resources Management Plan

### Vision Statement

"Georgia manages water resources in a sustainable manner to support the state’s economy, to protect public health and natural systems, and to enhance the quality of life for all citizens."
    Policy statement from the Comprehensive Statewide Water Management Planning Act signed by Governor Sonny Perdue on May 13, 2004.

#### Procedure for defining the vision

The vision statement above was provided in the final report of the Joint Comprehensive Water Plan Study Committee and then incorporated into the Comprehensive State-wide Water Management Planning Act. "This vision encompasses the concept of sustainability that has never been articulated in earlier goals. It also recognizes the interrelationship of the economy, environmental quality, and quality of life."

### Goals and Objectives

The statements of goals and objectives for the statewide water plan are quoted below, from EPD document of November 23, 2005, posted on Georgia Water Council website.
Goals - "The comprehensive water management plan will be drafted to meet two overarching goals:
* protect public health and environmental quality, and
* meet future needs while protecting aquifers, instream uses and downstream users"
Objectives - "To accomplish these goals we will focus on four management objectives:
   * Minimize withdrawals of water by increasing water conservation and reuse;
   * Maximize returns to the basin of origin through policies that address interbasin transfers, on-site sewage disposal systems, and land application of treated wastewater where water quantity is limited;
   * Meet instream and off stream demands for water through efficient surface storage, aquifer management and reducing water demands; and
   * Protect water quality by reducing pollutant loadings from discharges and runoff from the land to ensure the assimilative capacity of the streams is not exceeded and aquatic life is not impaired."
The new water policy tools (revised laws) to be developed for aiding the state comprehensive plan will be conceived and organized around these four water management objectives.

#### Procedure for defining the goals and objectives

Goals - A similar (slightly reworded) goals statement was given by Carol Couch at the first [Georgia Water Council] meeting on March 2, 2005 (see online meeting notes).
Objectives - The list of four management objectives was given in a presentation by Jim Kundell at the second Georgia Water Council meeting on June 7, 2005. At this meeting, Carol Couch reiterated the statements of goals and four objectives, and asked for the Council's concurrence, which was given.

### See also

Best Practices in defining vision and goals for a region, and examples from other states.