About This Lesson
Use Saving custom dashboard views to practice Japanese conversation, pronunciation, vocabulary, grammar, and quizzes.
Dialogue
A
ダッシュボードにカスタムビューを保存できるようにしてほしいです。
DASH-bohrd nee KAS-tum BYOO oh hoh-ZON deh-kee-roo YOH nee shee-teh HOH-shee dess. I would like the dashboard to save custom views.
B
複数のユーザーから、普段の設定を保存しておく方法がほしいという要望がありました。
foo-KOO-soo noh YOO-zah KAH-rah, foo-DAHN noh seh-TAY oh hoh-ZON shee-TEH oh-koo hoh-HOH gah HOH-shee ee-toh-yoo YOH-boh gah ah-ree-mah-shta. Several users have asked for a way to keep their usual setup.
A
毎週のレビュー中にフィルターを何度も切り替えると、時間が無駄になります。
MY-shoo noh ree-BYOO-CHOO-choo nee fee-ROO-tah oh NAHN-doh moh kee-ree-KAH-eh-roo toh, JEE-kahn gah moo-DAH nee nah-ree-mahss. Switching filters repeatedly wastes time during weekly reviews.
B
保存したビューがあれば、その作業をもっと速くできそうです。
hoh-ZON shee-tah BYOO gah ah-REH-bah, soh-noh sah-GYOH oh MOHT-toh hah-yah-KOO deh-kee-SOH dess. Saved views could make that routine faster.
A
ビューをチームメンバーと共有できると便利です。
BYOO oh CHEE-moo MEM-bah toh kyoh-YOO deh-kee-roo toh ben-REE dess. It would be useful if views could be shared with teammates.
B
共有には権限のルールが必要なので、それは別に扱うこともできます。
kyoh-YOO nee-wah ken-GEN noh ROO-roo gah hee-TSOO-yoh nah noh-deh, soh-REH wah BEH-tsoo nee ah-TSOO-kah-oo KOH-toh moh deh-kee-mahss. Sharing would need permission rules, so we could treat it separately.
A
個人用のバージョンだけでも、私の問題の大部分は解決します。
KOH-jeen-yoh noh BAH-john DAH-keh deh-moh, wah-TASH-ee noh MOHN-dye noh dye-boo-BOON wah kigh-KEH-tsoo shee-MAHss. Even a personal version would solve most of my problem.
B
それなら、最初の段階では個人用の保存ビューに集中できそうです。
soh-REH nah-rah, sai-SHOH noh dahn-KAI deh-wah KOH-jeen-yoh noh hoh-ZON BYOO nee shoo-CHOO deh-kee-SOH dess. Then the first step could focus on private saved views.Word by Word
ダッシュボード
“ダッシュボード” means the dashboard in this software context. It is the system area where the custom views are used and saved. New example: 管理画面のダッシュボードを開く means “open the administration dashboard.”
に
In “ダッシュボードにカスタムビューを保存できるようにしてほしいです,” “に” marks the dashboard as the thing that should be made able to save custom views. Here it does not simply mean “in.” New example: この画面に表示できるようにする means “make it possible to display it on this screen.”
カスタム
“カスタム” means custom or user-defined here, describing views configured for a particular need. It directly modifies “ビュー” in “カスタムビュー.” New example: カスタム設定 means “custom settings.”
ビュー
“ビュー” means a view of the dashboard, such as a particular arrangement or display of information. In the dialogue, it is the item the user wants to save and possibly share. New example: このビューを保存する means “save this view.”
を
In “カスタムビューを保存,” “を” marks “カスタムビュー” as the direct object being saved. It commonly follows the item affected by an action. New example: レポートを共有する means “share the report.”
保存
“保存” means saving or storing something for later use, as in “カスタムビューを保存.” It is used for keeping a view or setting available instead of configuring it again. New example: 設定を保存する means “save the settings.”
できる
In “保存できる,” “できる” means “can” or “be able to,” expressing that saving is possible. Together with “ようにしてほしい,” it describes the requested capability. New example: ファイルを編集できる means “can edit the file.”
よう
In “保存できるようにしてほしい,” “よう” is part of the expression meaning “so that it can be saved” or “so that saving becomes possible.” It connects a desired result with “してほしい.” New example: 誰でも使えるようにする means “make it so that anyone can use it.”
して
In “できるようにしてほしい,” “して” expresses making something reach the stated state: making it possible to save views. It is the connecting form used before “ほしい” in this request. New example: 使いやすくしてほしい means “I would like you to make it easier to use.”
ほしい
In “保存できるようにしてほしいです,” “ほしい” expresses that the speaker wants someone to make saving possible. This is a request for a change to the software, not simply the speaker’s desire to save something. New example: この機能を追加してほしい means “I would like you to add this feature.”
です
The “です” at the end of “してほしいです” gives the request a polite sentence ending. It makes the feature request suitable for a customer-support exchange. New example: 必要です means “it is necessary.”
複数
“複数” means several or multiple, referring here to more than one user in “複数のユーザー.” It is placed before “の” to describe the group of users. New example: 複数のファイル means “multiple files.”
の
In “複数のユーザー,” “の” links “複数” to “ユーザー” and makes the first word describe the second. The same linking pattern appears in “普段の設定.” New example: チームの設定 means “the team’s settings” or “settings for the team.”
ユーザー
“ユーザー” means users of the software. In “複数のユーザーから,” these users are the people who made the request. New example: ユーザーに通知する means “notify the user.”
から
In “複数のユーザーから,” “から” means “from” and identifies the users as the source of the requests. It commonly follows a person or group that provides information, feedback, or a request. New example: 顧客から連絡がありました means “there was contact from a customer.”
普段
“普段” means usually or ordinarily, referring to the normal routine in “普段の設定.” It describes the settings users normally use rather than a temporary arrangement. New example: 普段はこの画面を使います means “I usually use this screen.”
設定
“設定” means settings or setup here, referring to the user’s usual dashboard configuration. In “普段の設定を保存しておく,” it is the configuration that users want to keep. New example: 設定を変更する means “change the settings.”
おく
In “保存しておく,” “おく” means keeping something in a prepared or maintained state after doing it. The users want their usual setup saved in advance so it remains available later. New example: 必要な情報をメモしておく means “write down the necessary information in advance.”
方法
“方法” means a way or method, as in “普段の設定を保存しておく方法,” a way to keep the usual setup saved. It commonly follows an action when asking how that action can be done. New example: 問題を解決する方法 means “a way to solve the problem.”
が
In “方法がほしい,” “が” marks “方法” as the thing that is wanted. It is used here with “ほしい” to identify the desired item. New example: 新しい機能がほしい means “I want a new feature.”
という
In “ほしいという要望,” “という” introduces the content of the request: users wanted a way to keep their usual setup. It connects the preceding statement with the noun “要望.” New example: 変更したいという意見 means “an opinion saying that someone wants to make a change.”
要望
“要望” means a request or desired feature, specifically the users’ request for a way to keep their usual setup. It is the content later described as having existed or been received. New example: 新機能の要望を受ける means “receive a request for a new feature.”
ありました
In “要望がありました,” “ありました” means that there was such a request or that the request had been received. The polite form presents the request as an earlier fact in the support exchange. New example: 変更がありました means “there was a change.”
毎週
“毎週” means every week or weekly, identifying the recurring reviews in “毎週のレビュー.” It describes something that happens once each week. New example: 毎週会議をします means “we have a meeting every week.”
レビュー
“レビュー” means a review, here the regular weekly process in which the dashboard is checked. It is modified by “毎週の” in “毎週のレビュー.” New example: レビューの結果を確認する means “check the results of the review.”
中
In “レビュー中,” “中” means during or while an activity is in progress. “レビュー中に” means “during the review,” and “に” marks the time when the switching happens. New example: 作業中に連絡がありました means “there was contact during the work.”
フィルター
“フィルター” means the filter controls used to narrow or change the dashboard display. In the dialogue, these filters are switched repeatedly during weekly reviews. New example: フィルターを設定する means “set a filter.”
何度
In “何度も切り替える,” “何度” refers to repeated times, and with “も” it emphasizes that the switching happens many times. It describes the recurring action that wastes time. New example: 何度も確認する means “check repeatedly.”
も
In “何度も,” “も” adds the meaning of “even” or “as many as,” emphasizing the repeated number of times. This pattern is useful with a quantity or frequency expression. New example: 三回も試しました means “I tried it as many as three times.”
切り替える
“切り替える” means switch or change from one setting or option to another. Here it describes changing the dashboard filters repeatedly. New example: 表示を切り替える means “switch the display.”
と
In “切り替えると、時間が無駄になります,” “と” means “when” or “if,” linking the repeated switching to its automatic result. It presents the result as something that follows from that action. New example: このボタンを押すと画面が変わります means “when you press this button, the screen changes.”
時間
“時間” means time, specifically the time lost during the weekly review. In “時間が無駄になります,” it is the thing that ends up being wasted. New example: 時間を節約する means “save time.”
無駄
In “時間が無駄になります,” “無駄” means wasted or used without benefit. It describes the result of spending time repeatedly switching filters. New example: 無駄な作業 means “unnecessary or wasted work.”
なります
In “無駄になります,” “なります” means becomes or ends up as, showing the result that the time is wasted. The polite ending makes the statement suitable for the conversation. New example: 問題になります means “it becomes a problem.”
した
In “保存したビュー,” “した” is the form of “する” that modifies “ビュー” and means that the view has been saved. The whole phrase refers to views already saved for later use. New example: 変更した設定 means “the settings that were changed.”
あれば
In “保存したビューがあれば,” “あれば” means “if there is” or “if they are available.” It introduces the condition that saved views exist, leading to a possible improvement in the routine. New example: 時間があれば確認します means “if I have time, I will check.”
その
In “その作業,” “その” points back to the task just discussed, namely the repeated filter switching during weekly reviews. It lets the speaker refer to that already-mentioned task without repeating it. New example: その方法を使います means “I will use that method.”
作業
“作業” means the task or work being done, here the routine of repeatedly switching filters. “その作業” refers to the previously mentioned activity. New example: 作業を続ける means “continue the work.”
もっと
“もっと” means more, adding the idea of a greater degree in “もっと速く,” or “faster.” It is used before the word describing the improved result. New example: もっと簡単にする means “make it easier.”
速く
In “もっと速くできそう,” “速く” means faster, describing how the routine could be completed with saved views. It is the adverbial form used with “できる” to describe doing something quickly. New example: 速く処理する means “process it quickly.”
できそう
In “もっと速くできそうです,” “できそう” means seems possible or looks as if it can be done. Here it expresses a reasonable expectation that saved views could make the routine faster. New example: 明日なら対応できそうです means “it looks like we can handle it tomorrow.”
チーム
“チーム” means team, referring to the group the teammates belong to. It combines with “メンバー” in “チームメンバー.” New example: チームで作業する means “work as a team.”
メンバー
“メンバー” means member, and “チームメンバー” means team members. In the dialogue, these are the colleagues with whom views might be shared. New example: メンバーに共有する means “share it with the members.”
共有
“共有” means sharing something so that other people can access or use it. In the dialogue, it refers to sharing views with teammates and to the permission issues that sharing would create. New example: ファイルを共有する means “share a file.”
便利
In “便利です,” “便利” means useful or convenient. The speaker says that being able to share views with teammates would be useful. New example: この機能は便利です means “this feature is convenient.”
は
In “共有には権限のルールが必要,” “は” marks “共有には” as the topic and highlights what sharing requires. It can also give a topic a slight contrast with other parts of the discussion. New example: この方法は簡単です means “this method is easy.”
権限
“権限” means permission or access authority, referring to who is allowed to view or use shared views. It appears in “権限のルール,” rules governing that access. New example: 権限を確認する means “check the permissions.”
ルール
“ルール” means rules, here the rules needed to control sharing permissions. It is linked to “権限” in “権限のルール,” meaning rules about access authority. New example: 利用ルールを決める means “decide the usage rules.”
必要
In “権限のルールが必要,” “必要” means necessary or needed. It explains why sharing may need to be handled separately: permission rules would be required. New example: 確認が必要です means “confirmation is necessary.”
な
In “必要なので,” “な” links the adjective-like word “必要” to the reason marker “ので.” It creates the form needed before “ので” when giving a reason. New example: 重要なので確認してください means “because it is important, please check it.”
ので
In “必要なので,” “ので” means because or since and gives the reason for treating sharing separately. It presents the need for permission rules as the explanation. New example: 時間がないので、後で連絡します means “because I do not have time, I will contact you later.”
それ
In “それは別に扱う,” “それ” refers back to sharing, including its permission-rule requirements. It allows the speaker to refer to that topic without repeating “共有.” New example: それを確認します means “I will check that.”
別
In “別に扱う,” “別” means separately, indicating that sharing should be handled as a separate matter from the initial saved-view feature. It commonly appears before “に” when describing separate treatment. New example: この問題は別に考えます means “I will consider this problem separately.”
扱う
“扱う” means handle or treat, and in “別に扱う” it means deal with sharing as a separate feature or topic. It is useful when describing how a matter will be managed. New example: この問題を別に扱う means “handle this problem separately.”
こと
In “扱うこともできます,” “こと” turns the action “扱う” into the idea of handling it, allowing that possibility to be discussed. The phrase means that treating it separately is also possible. New example: 後で確認することができます means “it is possible to check it later.”
できます
In “別に扱うこともできます,” “できます” means can or is possible. It presents separate handling as an available option rather than a fixed decision. New example: オンラインで申し込むことができます means “you can apply online.”
個人用
“個人用” means for personal use, describing a version intended for one user rather than sharing with teammates. It modifies “バージョン” in “個人用のバージョン.” New example: 個人用のアカウント means “an account for personal use.”
バージョン
“バージョン” means version, here a personal-use version of the saved-view feature. The speaker says that even this limited version would solve most of the problem. New example: 最新バージョンを使う means “use the latest version.”
だけ
In “個人用のバージョンだけでも,” “だけ” means only or just, limiting the scope to the personal version. With “でも,” the phrase means that even that limited version would be sufficient. New example: 一部だけでも役に立ちます means “even just part of it is useful.”
で
In “個人用のバージョンだけでも,” “で” combines with “も” to mean that the personal version alone would be enough to produce the result. It marks the limited means or condition that can solve the problem. New example: この方法だけでも解決できます means “this method alone is enough to solve it.”
私
“私” means I or me, and in “私の問題” it identifies the speaker as the owner of the problem. It is followed by “の” to connect the speaker with the noun “問題.” New example: 私の設定を確認してください means “please check my settings.”
問題
“問題” means problem or issue, here the difficulty caused by repeatedly switching filters. “私の問題” means the speaker’s particular difficulty in the weekly review routine. New example: 問題を解決する means “solve the problem.”
大部分
“大部分” means most or the majority, referring to the greater part of the speaker’s problem. In “問題の大部分,” it follows “の” to specify what most of something is meant. New example: 作業の大部分が終わりました means “most of the work is finished.”
解決
“解決します” means solve or resolve, and here it describes what the personal version would do for most of the speaker’s problem. It focuses on removing the practical difficulty, not merely discussing it. New example: この機能で問題を解決する means “solve the problem with this feature.”
します
In “解決します,” “します” is the polite form used to say that the problem will be solved or resolved. It completes the verb expression “解決する” in a polite statement. New example: 後で確認します means “I will check it later.”
なら
In “それなら,” “なら” means “then” or “if that is the case,” responding to the previous point that a personal version would be enough. It introduces a conclusion based on what the other speaker has just said. New example: それなら、この案で進めます means “then, we will proceed with this plan.”
最初
“最初” means first or at the beginning. In “最初の段階,” it identifies the initial stage of developing the feature. New example: 最初に説明します means “I will explain first.”
段階
“段階” means stage or step, and “最初の段階” means the first stage of the work. It frames the personal saved-view feature as an initial development focus. New example: 次の段階で確認します means “I will check it at the next stage.”
集中
In “個人用の保存ビューに集中できそうです,” “集中” means focus effort or attention on something. The object of that focus is marked by “に,” and here it is the personal saved views. New example: この作業に集中する means “focus on this task.”
Grammar Points
～たり、～たりする
普段はフィルターを切り替えたり、設定を扱ったりする。
foo-DAHN wah fee-ROO-tah oh kee-ree-KAH-eh-tah-ree, seh-TAY oh ah-TSOO-KAHT-tah-ree soo-roo.Usually, I switch filters and handle settings.
This pattern lists representative actions. The final たり is followed by する to show that these are examples of what someone does.
NのためのN
チームメンバーのためのカスタムビューを保存する。
CHEE-moo MEM-bah noh tah-MEH noh KAS-tum BYOO oh hoh-ZON soo-roo.Save a custom view for team members.
「NのためのN」 means “N for N.” 「ための」 connects the intended user or purpose to a noun.
Japanese Vocabulary
カスタムビュー
noun
KAS-tum BYOO
custom view
ダッシュボード
noun
DASH-bohrd
dashboard
フィルター
noun
fee-ROO-tah
filter
レビュー
noun
ree-BYOO
review
何度も
adv
NAHN-doh moh
repeatedly; many times
切り替える
verb
kee-ree-KAH-eh-roo
to switch; to change
設定
noun
seh-TAY
settings; setup
普段
adv
foo-DAHN
usual; ordinarily
複数
det
foo-KOO-soo
several; multiple
保存
noun
hoh-ZON
saving; storage
毎週
adv
MY-shoo
weekly; every week
要望
noun
yoh-BOH
request; demand
Quiz
Spelling
Tap the letters to spell the word.
custom view
Show Answer
カスタムビューdashboard
Show Answer
ダッシュボードreview
Show Answer
レビューfilter