OpenLLM-France/wikimedia huggingface dataset:
# Models and Theories in Human-Computer Interaction/The Economics of TAM

The Technology Acceptance Model (TAM) is a model for describing the likeliness of an innovation’s usage by a user based on self-perceived notions of usefulness and ease of use.
The increasing ubiquity of technology has greatly changed the implications of TAM, which was originally developed at a time where technology was only available at the workplace. Today, the role of technology has expanded to every aspect of our daily lives. In effect, the decision to adopt a technology has an increasingly prominent impact in day-to-day events.
Unfortunately, the validity of TAM has historically relied on self-assessment methods in studies with users. These methods rely on the assumption that a person can accurately assess and report his/her emotional experiences. While self-reports offer insights into the subjective user experience, they do not explain the rationale behind user behaviors. Therefore, models that help explain the human decision making process should be examined for usage in conjunction with TAM.
In economic theory, human behavior is similarly modeled on one’s own perception and their actual actions though the model of the Economic Man.The Economic Man model depicts human actions as the result of choosing the best option based on the fulfillment of his or her "utility function", meaning the ability to maximize any situation that involves choice. Adam Smith’s Wealth of Nations introduced the idea of the Invisible Hand, a subconscious force in free markets to adjust prices through the collective self-interested actions of all individuals. Smith proposed that the economic man is driven by a relentless desire to improve his condition; a common self-seeking trait of humanity. This model of humanity proved instrumental in relating economic behavior to individual psychology and shaped the course for modern economic theory.
The underlying human factors principles of HCI has allowed for widespread multidisciplinary integrations within the field. The commonalities between the two models and their focus on subconscious human motivations for predicting actual behavior is representative of the basis of human nature. Ease of use and usefulness are directly applicable to the economic human variable of utility. If a user does not think an innovation will add to their utility, then they will not adopt its usage into their processes.
By combining the similarities of TAM and the Economic Man, we can further explore the user's rationale behind their decision to use a particular innovation, which could lead to a more comprehensive understanding of user behavior.
# Models and Theories in Human-Computer Interaction/TAM proponent of perceived intention but not behavioral intention

As per the TAM’s model, user’s intention towards the adaption of a technology is channeled by the following two attributes: perceived usefulness (PU) and perceived ease of use (PEU). Also, the model provides a base that would allow prediction of the use of future technologies. The IS community do find that the TAM to be a powerful model but the application benefits are minimized by limitations.

### TAM’s limitations:

Perceived utility and perceived ease of an application may not necessarily determine the adoption of new technologies by a user. According to Straub (1995), perceived use can influence morale, disposition and ultimately performance but the relationship is not as straightforward as the basic TAM model implies. The influence (social influences and cognitive instrumental process) can skew the perceived intention of use. Hence, PU and PEU are not reliable indicators as to the behavioral intention of usage. Behavioral intention can change the actual usage of a technology. For example, a user is interested in the process of adopting a running app (smartphone) as a fitness regimen. The app meets user’s perceived utility and perceived ease of use by providing enhanced user-interface with advanced features. While, PU and PEU forces perceived intention – it is actually the user’s behavioral intention (the motivation or aspiration to run) that may decided the actual intention. Hence, it can be determined that perceived utility and perceived ease of use may not fully explain behavioral intentions towards the use of a technology.
Sources:
V. Venkatesh, M.G. Morris, G.B. Davis, F.D. Davis, User acceptance of information technology: toward a unified view, MIS Quart., 27 (3) (2003), pp. 425–478 Straub, D., Limayem, M., and Karahanna-Evaristo, E. Measuring system usage – implications for IS theory testing, Management Sci- ence 41(8), (1995) 1328–1342.
# Models and Theories in Human-Computer Interaction/The Active Wiki
### The Active Wiki (Brian Buehler)

The wiki environment would not exist without computers. When the Internet was first being established, it was done to provide a means in which to share information and research quickly among people far away from each other. This in itself spawned many different forms of sharing information, one of them being the wiki environment. Wiki is unique in that information is written by the masses, and thusly read and corrected by the masses. Cognition among everyone involved in writing a wiki page is shared and stored for future users.
Caroll stated that Activity Theory rejects the isolated human being as an adequate unit of analysis, insisting on cultural and technical mediation of human activity. One person is simply not enough to create a well thought out object based on this theory. This is where the Wiki environment shines. Thoughts, ideas, and facts are captured and mediated by the Wiki tool. Multiple users can come together both near and far and allow all of them to create content that they can call their own as their schedules permit. Even in this class, students are taking this course online from several locations around the US. They are able to post information to the Wiki page and build on each others thoughts and ideas to create a well founded object. Distance is not “seen” when interacting in this environment and brings people closer and simulates the individuals being in the same room at the same time.
However, the Wiki environment can deter interaction by some as it generally allows anyone to edit. If everyone contributing has the same goal in mind, this is a good thing, however this cannot be guaranteed. Most of the facts will be captured, but there is possibility that something is stated wrong and not corrected, which can lead to future mis-quoting in other research.
Even as time passes, the Wiki environment is generally recognized as a useful tool for collaboration and is being implemented in the workplace more and more. Human activity will continue to change and evolve, but the founded concepts of Activity Theory will remain as they try to understand the dynamics between hierarchically structured activity and computer use.
# Models and Theories in Human-Computer Interaction/TAM and Engineering

The technology acceptance model was a little more relate-able to me, especially since I work on engineering software. In our industry, engineers are reluctant to change because they get comfortable working in a system and may even have existing projects that have already been created and managed in another system. For us, it can be difficult for new designs to be accepted even though they may be more usable. I believe that many of our users already have a negative attitude towards using new software because they may feel that it will make their work more difficult and they will have to learn a new system.
The current systems are quite difficult to use and many users complain about it, but at the same time, they have taken the time to learn it and can use it. A new interface means they need to learn how to use it again and they may remember the experiences they had when trying to learn the current system. Davis does not mention how previous experiences could affect the attitude and perceived ease of use of the new technology which are both important factors as I think that perceived usefulness exists with the users, especially if a new, useful feature has been added.
I can understand the reluctance our engineers have to using new technologies, but if we can truly provide a useful product, demo the ease of use, and provide successful marketing we can try to gain more acceptance from users.
# Models and Theories in Human-Computer Interaction/TAM as an Outline in Need of Thoughtful Modifications
### TAM as an Outline in Need of Thoughtful Modifications (Breann Bowe)

When considering the likelihood of acceptance of a form of technology, I believe the Technology Acceptance Model (TAM) is a useful starting point. However, as a standalone model, I don’t think it is detailed enough to account for all of the variables a group of users brings to the table. Later modifications to the Final TAM version have begun to address these variables but risk making the model unwieldy and impractical.
For example, at work I’ve been tasked with increasing the nursing department’s use of an optional feature within the electronic medical record (EMR). Knowing that “perceived usefulness” and “perceived ease of use” play a large part in a nurse’s decision to use this technology, I plan on focusing my training on the simplicity and worth of this feature. As the use of this feature is an optional step in a mandatory process, I need to consider additional variables to make my approach a “better sell.” Still, these variables will be things I have to add onto the TAM myself.
Simply put, I do agree with the Technology Acceptance Model. However, I think it should be used as more of an outline with modifications thoughtfully made to better suit the needs of the assessor. There is no doubt that “perceived usefulness” and “perceived ease of use” are important points to consider, but there are also additional field-specific variables that may provide important insight in the prediction of technology acceptance.
# Models and Theories in Human-Computer Interaction/TAM in software updates
### TAM in software updates

As seen in a previous section discussing TAM, two main components are perceived usefulness of the technology and perceived ease of use. These in turn (according to Davis' original proposal regarding user's motivation in 1985) influence a user's attitude toward using the new technology. While TAM is supposed to be able to be a more quantitative measurement, it in turn underestimates the more qualitative issues involved in a user's attitude. The time it took a user to learn how to use the current software is not trivial and not all users' are going to be satisfied with having to relearn applications and programs as software is updated. A relatively recent example of user dissatisfaction of this case would be when Facebook (social media) pushes forward new user interfaces of its website. Both younger and older users will complain on the social media outlets about the new interface and how it isn't the same or not as good as the previous. This is not necessarily based on the true quality of the interface (although it may have issues) but rather on the user's unfamiliarity and sense of loss. The user loses their perceived ease of use when new software updates occur and the time lost having to learn or relearn software based on updates can affect the user's perceived usefulness of the software update as well. When an academic institution rolls out a new website or new Internet-based learning tool, the bugs that inevitably need to be found and corrected during the time after the rollout will affect users' ability to use the tools effectively on top of the issues seen in the Facebook (social media) example. If these issues are not given proper weight in TAM, then TAM itself does not properly account for the system use that will occur by the user as an end result.
# Models and Theories in Human-Computer Interaction/TAM in the Workplace
## TAM in the Workplace (Jeff Bazer)

In the Technology Acceptable Model (TAM), users are forced to use a new system or technology related item all at a certain point vs the diffusion of innovation in letting the user decide when to upgrade. I see TAM used a lot in corporate environments with software upgrades and enhancements. In the original TAM proposed by Fred Davis there is a user motivation section which contains perceived usefulness, perceived ease of use and attitude toward using. In my experience, there are users who fit into two categories - ones who are excited for something new and perceived to be easier and ones who don’t like change and are happy with how they do their job today. Then outside of that, there is the actual system use, so once the system has gone live and users are actually using the new system.
A very recent example of TAM is at work we were rebuilding one of our financial tools from a system that was dated by about 10 years. The system was finally ready to go live and there were trainings ahead of time, but the trainings consisted of someone standing in front of the room and showing users the new system - they were not allowed to go in and play with the new system early and try to get a feel for it. All the users left friday with the old system and came back Monday with the new system and there was a ton of confusion. To top all of that off, there ended up being bugs in the new system that made working even harder until an emergency fix went into place two days later.
While I don't always fully agree with TAM, I do think that it can be done well or very poorly. TAM is something that happens all the time in all kinds of fashion and has much room for improvement.
# DESCRIPTION:

Returns the remainder of first value divided by second.
// is an op value.

# ARGUMENTS

* value1 -- (Type: number pair char money time tuple)
* value2 -- (Type: number pair char money time tuple)
# DESCRIPTION:

Prints a variable name followed by its molded value. (for debugging)
?? is a function value.

# ARGUMENTS

* name -- (Type: any)
# DESCRIPTION:

Returns TRUE if the values are identical.
=? is an op value.

# ARGUMENTS

* value1 -- (Type: any)
* value2 -- (Type: any)
# DESCRIPTION:

Returns TRUE if the values are equal and of the same datatype.
== is an op value.

# ARGUMENTS

* value1 -- (Type: any)
* value2 -- (Type: any)
# Rebol Programming/?xml

No information on ?xml (word has no value)
# Rebol Programming/Advanced

Collection of essays on more advanced topics - please state authorship here
# DESCRIPTION:

Returns TRUE if the values are equal.
= is an op value.

# ARGUMENTS

* value1 -- (Type: any)
* value2 -- (Type: any)
# DESCRIPTION:

Prints information about words and values.
? is a function value.

# ARGUMENTS

* word -- (Type: any-type)
# Japanese/Vocabulary/Government and politics

| Japanese | English | Reading | Notes |
| 政治 | government | せいじ | |
| 共産主義 | communism | きょうさんしゅぎ | |
| 民本主義 | democracy | みんぽんしゅぎ | |
| 選出 | election | せんしゅつ | |
| 政府 | government | せいふ | |
| 与党 | government party | よとう | |
| 野党 | opposition party | やとう | |
| 議会 | parliament | ぎかい | |
| 大統領 | president | だいとうりょう | the president of a country |
| 総裁 | president | そうさい | the president of a party |
| 総理大臣 | prime minister | そうりだいじん | |
| 共和国 | republic | きょうわこく | |
# Japanese/Vocabulary/Health

| Japanese | English | Reading |
| 病気 | sickness | びょうき |
| 具合 | condition | ぐあい |
| 頭痛 | headache | ずつう or あたまいた |
| 歯痛 | toothache | はいた or しつう |
| 胃痛 | stomachache | いつう |
| 鼻水 | runny nose | はなみず |
| 咳 | cough | せき |
| 熱 | fever | ねつ |
| 目眩 (or 眩暈) | dizzy | めまい |
| 風邪 | cold | かぜ |
| (流感) | influenza | インフルエンザ (or りゅうかん) |
| 薬 | medicine | くすり |
| 注射 | injection | ちゅうしゃ |
# Japanese/Vocabulary/Law
## Law

| Japanese | English | Reading |
| 法律 | Law | ほうりつ |
| 犯罪学 | Criminology | はんざいがく |
| 法曹 | Legal Worker | ほうそう |
| 検察官 | Prosecutor | けんさつかん |
| 弁護士 | Barrister | べんごし |
| 裁判所 | Court | さいばんしょ |
| 最高裁判所 | Supreme Court | さいこうさいばんしょ |
| 高等裁判所 | High Court | こうとうさいばんしょ), abbreviated 高裁 (こうさい) |
| 地方裁判所 | District Court | ちほうさいばんしょ), abbreviated 地裁 (ちさい) |
| 簡易裁判所 | Summary Court | かんいさいばんしょ |
| 人権 | Human rights | じんけん |

## General terms

| Japanese | English | Reading | Notes |
| 出願 | Application | しゅつがん | |
| 暫定 | Provisional | ざんてい | |

## Criminal law (刑法 けいほう)

| Japanese | English | Reading |
| 犯罪 | Crime | はんざい |
| 強迫 | Assault | きょうはく |
| 陰謀 | Conspiracy | いんぼう |
| 詐欺 | Fraud | さぎ |
| 殺人 | Homicide | さつじん |
| 過失致死罪 | Involuntary manslaughter | かしつちしざい |
| 偽証 | Perjury | ぎしょう |
| 強姦 | Rape | ごうかん |
| 盗難 | Theft | とうなん |
| 被疑者 | Suspect | ひぎしゃ |
| 逮捕 | Arrest | たいほ |
| 刑罰 | Punishment | けいばつ |
| 死刑 | Capital punishment | しけい |
| 懲役 | Imprisonment at hard labor | ちょうえき |
| 禁錮 / 禁固 | Imprisonment not at hard labor | きんこ |
| 罰金 | Fine | ばっきん |
| 保釈 | Bail | ほしゃく |
| 保護観察 | Probation | ほごかんさつ |

## Corporate law (会社法 かいしゃほう)

| Japanese | English | Reading |
| 会社 | Company | かいしゃ |
| 合名会社 | Partnership | ごうめいかいしゃ |
| 合資会社 | Limited partnership | ごうしがいしゃ |
| 株式会社 | Corporation | かぶしきがいしゃ |
| 有限会社 | Limited company | ゆうげんかいしゃ |
| 設立 | Incorporation | せつりつ |
| 定款 | Articles of incorporation | ていかん |
| 有限責任 | Limited liability | ゆうげんせきにん |
| 取締役 | Director | とりしまりやく |
| 取締役会 | Board of directors | とりしまりやくかい |
| 取締役会長 | Chairman of the board | とりしまりやくかいちょう |

## Intellectual property (知的財産 ちてきざいさん)

| Japanese | English | Reading |
| 著作権 | Copyright | ちょさくけん |
| 所有者 | Holder (of right) | しょゆうしゃ |
| 侵害 | Infringement | しんがい |
| 特許 | Patent | とっきょ |
| 特許出願 | Patent application | とっきょしゅつがん |
| 特許出願中 | Patent pending | とっきょしゅつがんちゅう |
| 弁理士 | Patent attorney | べんりし |
| 特許審査官 | Patent examiner | とっきょしんさかん |
| 特許庁 | Patent office | とっきょちょう |
| 保護 | Protection | ほご |
| 商標 | Trademark | しょうひょう |
| 登録 | Registration | とうろく |
# Japanese/Vocabulary/Family and people
## Family and people

| Japanese | English | Reading |
| 家族 | /(n) family/members of a family/(P)/ | かぞく |
| お母さん/母さん | /(n) (hon) mother/(P)/ | おかあさん/かあさん |
| お父さん/父さん | /(n) (hon) father/(P)/ | おとうさん/とうさん |
| 兄弟 | /(n) (hum) siblings/(P)/ | きょうだい |
| 姉 | /(n) (hum) older sister/(P)/ | あね |
| お姉さん/姉さん | /(n) (hon) older sister/(vocative) "Miss?"/(P)/ | おねえさん/ねえさん |
| 兄 | /(n) (hum) older brother/(P)/ | あに |
| お兄さん/兄さん | /(n) (hon) older brother/(vocative) "Mister?"/(P)/ | おにいさん/にいさん |
| 妹 | /(n) (hum) younger sister/(P)/ | いもうと |
| 弟 | /(n) younger brother/faithful service to those older/brotherly affection/ | おとうと |
| お爺さん/おじいさん | /(n) grandfather/male senior-citizen/ | おじいさん |
| お婆さん/おばあさん | /(n) grandmother/female senior-citizen/ | おじいさん |
| Japanese | English | Reading |
| 奥様/奥さん | /(n) (hon) wife/your wife/his wife/married lady/madam/(P)/ | おくさま/おくさん |
| 家内 | /(n) (hum) wife/(P)/ | かない |
| 御主人 | /(n) (hon) your husband/her husband/ | ごしゅじん |
| Japanese | English | Reading |
| 伯母 | /(n) (hum) aunt (older than one's parent)/ | おば |
| 叔母 | /(n) aunt (younger than one's parent)/(P)/ | おば |
| 伯父 | /(n) (hum) uncle (older than one's parent)/ | おじ |
| 叔父 | /(n) uncle (younger than one's parent)/(P)/ | おじ |
| Japanese | English | Reading |
| 女 | /(n) woman/girl/daughter/ | おんな |
| 男 | /(n) man/(P)/ | おとこ |
| 女の子 | /(n) girl/(P)/ | おんなのこ |
| 男の子 | /(n) boy/(P)/ | おとこのこ |

## Occupations

| Japanese | English | Reading |
| 店員 | shop assistant | てんいん |
| 俳優 | actor, actress | はいゆう |
| 医者 | doctor | いしゃ |
| 教師 | teacher (academic) | きょうし |

## Related resources

"For Japanese, family names are the worst growing pains"
# Japanese/Vocabulary/Food and drink
## Foods (食べ物)

| Japanese | English | Reading |
| 食べ物 | Food | たべもの |
| 肉 | Meat | にく |
| 御飯 / ご飯 | Rice (cooked); (also Meal) | ごはん |
| 米 | Rice (uncooked) | こめ |

### Fruit (果物)

| Japanese | English | Reading | Notes |
| 林檎 / 苹果 | Apple | リンゴ | Also written equally as often in Hiragana. |
| | Orange | オレンジ | |
| 梅 | Japanese plum | うめ | |
| 西瓜 | Watermelon | すいか | |
| 葡萄 | Grape | ぶどう | |
| 西洋梨 | Pear | せいようなし | |
| | Grapefruit | グレープフルーツ | |
| 甘蕉 | Banana | バナナ | |
| 桜桃 | Cherry | さくらんぼ | |
| 苺 / 莓 | Strawberry | いちご | |
| 桃 | Peach | もも | |

### Vegetables (野菜)

| Japanese | English | Reading |
| 野菜 | Vegetable | やさい |
| 人参 / 人蔘 | Carrot | にんじん |
| 玉ねぎ / 玉葱 | Onion | たまねぎ |
| 葱 | Spring (green) onion | ねぎ |

### Spices & Condiments

| Japanese | English | Reading | Notes |
| 胡椒 | Pepper | こしょう | |
| 塩 | Salt | しお | |

### Pastry

| Japanese | English | Reading | Notes |
| ケーキ | Cake | | |

## Drink (飲み物)

| Japanese | English | Reading |
| 飲み物 | Drink | のみもの |
| 水 | Water | みず |
| (お)茶 | Green Tea | おちゃ |
| 紅茶 | Black tea | こうちゃ |
| 珈琲 | Coffee | コーヒー |
| 牛乳 | Milk | ぎゅうにゅう |
| | Milk | ミルク |
| | Juice | ジュース |
| | Orange juice | オレンジジュース |

### Alcoholic beverages (酒)

| Japanese | English | Reading |
| 酒 | Alcoholic beverages in general | さけ |
| | Alcoholic beverages in general | アルコール >> Highball |
| 梅酒 | Plum wine | うめしゅ |
| 日本酒 | Sake; Japanese rice wine | にほんしゅ |
| 麦酒 | Beer | ビール |
| 生ビール | Draft beer | なまビール |
| | Wine | ワイン |
| | Sherry | シェリー |
| 三鞭酒 | champagne | シャンパン |
| 白ワイン | White wine | しろワイン |
| 赤ワイン | Red wine | あかワイン |
| 焼酎 | Distilled spirits; liquor | しょうちゅう |
| | Whiskey | ウィスキー |
| | Vodka | ウォッカ |
| | Gin | ジン |
| | Scotch | スコッチ |
| | Tequila | テキーラ |
| | Brandy | ブランデー |
| | Rum | ラム |
# Japanese/Vocabulary/Gairaigo

Gairaigo (外来語) are words of foreign origin.
| Japanese | English | Reading | Notes |
| アルバイト | Arbeit | | German: Part-time job |
| 麦酒 | Beer | ビール | Dutch: Bier |
| カメラ | Camera | | |
| 倶楽部 | Club | クラブ | |
| 珈琲 | Coffee | コーヒー | Dutch: Koffie |
| ダンス | Dance | | |
| ドル | Dollar | | |
| ドア | Door | | |
| ダブル | Double | | |
| エレベーター | Elevator | | |
| エスカレーター | Escalator | | |
| 硝子 | Glass | ガラス | Dutch: Glas |
| ハート | Heart | | |
| ヘリコプター | Helicopter | | |
| ホームラン | Home Run | | |
| イメージ | Image | | |
| ライオン | Lion | | |
| リンク | Link | | |
| マップ | Map | | |
| メモ | Memo | | |
| ネクタイ | Necktie | | |
| ニュース | News | | |
| 麺麭 | Bread | パン | Portuguese: Pan |
| 頁 | Page | ページ | |
| 洋琴 | Piano | ピアノ | Italian: Pianoforte |
| プレゼント | Present | | |
| ペン | Pen | | |
| ラジオ | Radio | | |
| レストラン | Restaurant | | |
| ロマンス | Romance | | |
| サラダ | Salad | | |
| スープ | Soup | | |
| スペシャル | Special | | |
| スポーツ | Sports | | |
| スパイ | Spy | | |
| スーパー | Supermarket | | |
| 煙草 / 莨 | Tobacco | タバコ | Portuguese: Tabacco |
| 天麩羅 | Tempura | テンプラ | Portuguese: Têmpora |
| テスト | Test | | |
| テキスト | Text | | |
| トイレ | Toilet | | |
| 蕃茄 | Tomato | トマト | |
| ワイン | Wine | | |
| 零 | Zero | ゼロ | |
| ズボン | Zubon (trousers) | | French: Jupon |
# Japanese/Vocabulary/Geology

* Japanese/Vocabulary/Meteorology
* Japanese/Vocabulary/Weather and seasons
| Japanese | English | Reading |
| 石 | stone | いし |
| 海岸 | beach, coast | かいがん |
| 草 | grass | くさ |
| 坂 | hill | さか |
| 島 | island | しま |
| 砂 | sand | すな |
| 谷 | valley | たに |
| 湖 | lake | みずうみ |
| 森 | forest | もり |