About This Lesson
Use Discussing saved dashboard views and sharing permissions to practice Korean conversation, pronunciation, vocabulary, grammar, and quizzes.
Dialogue
A
대시보드에서 사용자 지정 보기를 저장할 수 있으면 좋겠습니다.
dae-shee-BOH-duh-eh-suh sah-yong-jah jee-jung BOH-gee-reul juh-jang-hal soo ee-sseu-myun joh-ket-seum-nee-dah. I would like the dashboard to save custom views.
B
여러 사용자가 평소 설정을 유지할 수 있는 방법을 요청했습니다.
YUH-ruh sah-yong-jah-gah pyung-soh suhl-jung-eul yoo-jee-hal soo een-neun bang-bop-eul yo-cheong-haet-seum-nee-dah. Several users have asked for a way to keep their usual setup.
A
주간 검토 중에 필터를 계속 바꾸면 시간이 낭비됩니다.
joo-GAHN gum-toh joong-eh FEEL-tuh-reul gyeh-sok bah-koo-myun shee-gahn-ee nang-bee-doem-nee-dah. Switching filters repeatedly wastes time during weekly reviews.
B
저장된 보기를 사용하면 그 반복 작업을 더 빠르게 처리할 수 있습니다.
juh-jang-dwen BOH-gee-reul sah-yong-ha-myun guh ban-bok jah-up-eul duh PPAH-reu-geh chuh-ree-hal soo eet-seum-nee-dah. Saved views could make that routine faster.
A
보기를 팀원들과 공유할 수 있다면 유용할 것 같습니다.
BOH-gee-reul teem-won-deul-gwah gong-yoo-hal soo eet-dah-myun yoo-yong-hal gut gat-seum-nee-dah. It would be useful if views could be shared with teammates.
B
공유 기능에는 권한 규칙이 필요하므로, 그 부분은 별도로 다룰 수 있습니다.
gong-yoo gee-neung-eh-neun G WUHN-han gyoo-cheek-ee pee-ryo-ha-mu-ro, guh boo-boon-eun byul-doh-ro dah-rool soo eet-seum-nee-dah. Sharing would need permission rules, so we could treat it separately.
A
개인용 버전만 있어도 제 문제의 대부분을 해결할 수 있을 것입니다.
gae-in-yong buh-jeon-man ee-suh-doh jeh moon-jeh-eh dae-boo-boon-eul hae-gyul-hal soo eet-seul gut-im-nee-dah. Even a personal version would solve most of my problem.
B
그렇다면 첫 단계에서는 비공개 저장 보기에 초점을 맞출 수 있겠습니다.
guh-reut-dah-myun chut dan-gye-eh-suh-neun bee-gong-gae juh-jang BOH-gee-eh cho-jum-eul mat-chool soo eet-get-seum-nee-dah. Then the first step could focus on private saved views.Word by Word
대시보드에서
'대시보드에서' means 'in the dashboard' here, with 에서 marking where the saving action takes place. Use a place noun with 에서 when describing where an action happens; in this scene, the customer is discussing work inside a dashboard.
사용자
'사용자' means 'user', referring to someone who uses the software. It can appear before another noun to identify something related to users, as in 사용자 지정; this form is useful in software support discussions.
지정
'지정' contributes the idea of a user-selected or custom designation in 사용자 지정. It is useful when describing an item configured for a particular purpose, here a dashboard view chosen by the user.
보기를
'보기를' means 'the view' as the object being saved, with 를 marking it as the object of the action. The object-marker pattern is useful after an action verb; here the customer asks for the dashboard to save a view.
저장할
'저장할' means 'to save' in the possibility phrase 저장할 수 있으면. It is the form of 저장하다 used before the possibility noun 수, a pattern useful for describing whether a software item can be saved.
수
'수' expresses ability or possibility in 저장할 수 있으면. The pattern of a verb form followed by 수 and a form of 있다 is useful when discussing whether a feature can perform an action; here the action is saving a view.
있으면
'있으면' supplies the conditional 'if it is possible' part of 저장할 수 있으면. The conditional form is useful for making a request based on a possible feature, as the customer does here.
좋겠습니다
'좋겠습니다' means 'would be good' and makes the request polite and indirect. It is useful when suggesting a desirable feature to a support representative rather than giving a direct command.
여러
'여러' means 'several' and indicates more than one user before 사용자. It is useful before a noun when referring to a number of people or things without giving an exact number; here it broadens the request beyond one customer.
사용자가
'사용자가' means 'users' as the subject of the request, with 가 marking 사용자 as the subject. The subject-marker pattern is useful when identifying who performed an action; here the users made the request.
평소
'평소' refers to what is usual or normally done, describing the users' regular setup. It is useful before a noun or action when discussing normal habits, as in maintaining the setup used for routine reviews.
설정을
'설정을' means 'the setup' or 'settings' as the object being maintained, with 을 marking it as the object. This object pattern is useful after an action such as maintaining or changing settings; here users want to keep their usual configuration.
유지할
'유지할' means 'to keep' or 'maintain' in 유지할 수 있는 방법. It is the form of 유지하다 used before the possibility phrase, and it is useful when describing preserving an existing setup or state.
있는
'있는' comes from 있다 and modifies 방법 in 유지할 수 있는 방법, making the phrase refer to an available way. The pattern of a modifying clause before 방법 is useful when describing a method for carrying out an action; here it means a way to keep the usual setup.
방법을
'방법을' means 'a way' or 'method' as the object of the request, with 을 marking it as the object. Noun plus the object marker is useful when asking for or requesting a method; here users requested a way to keep their setup.
요청했습니다
'요청했습니다' means 'requested' and presents the request as completed in a formal polite style. The pattern of an object followed by 요청하다 is useful in support contexts when reporting what users asked for.
주간
'주간' means 'weekly' and specifies the regular timing of the reviews in 주간 검토. It is useful before an activity noun when identifying a weekly schedule; here it describes recurring review work.
검토
'검토' means 'review' in 주간 검토, referring to the regular examination of dashboard information. It can be used as a noun for an evaluation or checking activity; here it names the work during which filters are changed.
중에
'중에' means 'during' in 검토 중에, marking the period while the review is taking place. The pattern of an activity noun followed by 중에 is useful for locating an event within an ongoing activity; here the time loss happens during weekly reviews.
필터를
'필터를' means 'filters' as the object being changed, with 를 marking the object of 바꾸다. This pattern is useful when describing which software setting an action affects; here the filters are changed repeatedly.
계속
'계속' means 'continuously' or 'repeatedly' and describes the repeated filter changes. It commonly comes before an action to show that it continues over time; here it emphasizes the inefficient repetition during reviews.
바꾸면
'바꾸면' means 'if or when changing' and forms the condition in 필터를 계속 바꾸면. It comes from 바꾸다 with the conditional ending 면, a useful pattern for explaining what happens when a user changes a setting.
시간이
'시간이' means 'time' as the subject of the statement, with 이 marking time as what is wasted. The subject-marker pattern is useful when identifying what experiences a result; here the result is wasted time.
낭비됩니다
'낭비됩니다' means 'is wasted' in a formal polite form, describing the result for time. The form of 낭비되다 is useful for reporting inefficiency without naming a person as the cause; here repeated filter changes waste time.
저장된
'저장된' means 'saved' and modifies 보기, identifying a view that has been stored. It comes from 저장되다 and is useful before a noun when describing a completed saved state; here saved views make the routine faster.
사용하면
'사용하면' means 'if or when using' and introduces the condition in 저장된 보기를 사용하면. It comes from 사용하다 with 면, a useful form for linking the use of a software feature to its result; here using a saved view makes the task faster.
그
'그' means 'that' and points back to the routine already being discussed. It is useful before a noun when referring to something known from the conversation; here it identifies the recurring task connected with repeated filter changes.
반복
'반복' means 'repetition' or 'recurring' in 반복 작업, describing work that happens repeatedly. It is useful before a noun to identify recurring activity; here it characterizes the routine that saved views could speed up.
작업을
'작업을' means 'the task' or 'work' as the object being handled, with 을 marking the object. This pattern is useful after a verb describing processing or handling; here the recurring task is completed more quickly.
더
'더' means 'more' and makes the following speed comparison stronger in 더 빠르게. It commonly comes before an adjective or adverb in a comparative expression; here it means faster than the current routine.
빠르게
'빠르게' means 'quickly' or 'faster' and describes how the task can be handled. It is the adverbial form of 빠르다 and commonly comes before an action; 더 supplies the comparative meaning in this sentence.
처리할
'처리할' means 'to handle' or 'process' in 처리할 수 있습니다. It is the form of 처리하다 used before the possibility construction, and it is useful for describing how software or a person deals with a task.
있습니다
'있습니다' completes the formal polite possibility expression 처리할 수 있습니다, meaning that the task can be handled. This form is useful in professional explanations of available functions; here it states the benefit of using saved views.
팀원들과
'팀원들과' means 'with teammates', with the ending 과 expressing accompaniment alongside 팀원들. The pattern of a person or group followed by 과 is useful for describing who receives or joins an action; here views may be shared with teammates.
공유할
'공유할' means 'to share' in 공유할 수 있다면. It is the form of 공유하다 used before the possibility phrase, and it is useful when describing making a software item available to other people.
있다면
'있다면' means 'if it is possible' in 공유할 수 있다면. It comes from 있다 with the conditional ending 면 and is useful for presenting a feature as a condition; here the usefulness depends on whether views can be shared.
유용할
'유용할' means 'useful' in 유용할 것 같습니다. It is the form of 유용하다 used before 것, and it is useful for giving a tentative evaluation of a feature; here sharing views is described as potentially useful.
것
'것' turns the preceding idea into the nominal expression 유용할 것 같습니다, which means 'it seems it would be useful'. This pattern is useful for making a cautious assessment about a feature rather than stating the evaluation too directly.
같습니다
'같습니다' means 'seems' or 'appears' in 유용할 것 같습니다 and gives the evaluation a formal polite, tentative tone. The pattern ending in 것 같습니다 is useful when expressing a careful opinion in a support conversation.
공유
'공유' means 'sharing' as a noun in 공유 기능, identifying the feature concerned with sharing. It is useful before a noun such as 기능 when naming a software capability; here the sharing capability is considered separately from saved views.
기능에는
'기능에는' marks the sharing feature as the area to which the need for permission rules applies. The ending 에는 combines 에 with a topic marker, a useful pattern for setting the scope of a statement; here the scope is the sharing feature.
권한
'권한' means 'permission' or 'access rights' in 권한 규칙. It identifies the access control involved in sharing a view; this term is useful when discussing who may use or see a software feature.
규칙이
'규칙이' means 'rules' as the subject of the statement, with 이 marking the rules as what is needed. The subject-marker pattern is useful when identifying the requirement in a sentence; here permission rules are required for sharing.
필요하므로
'필요하므로' means 'because it is needed' and gives the reason for treating sharing separately. It comes from 필요하다 with the formal reason ending 으므로, a useful pattern for explaining a requirement in professional discussion.
부분은
'부분은' means 'as for that part' or 'that aspect', with 은 setting it as the topic. Here it refers to the sharing and permission aspect; this pattern is useful when separating one part of a larger feature discussion.
별도로
'별도로' means 'separately' and modifies how the sharing aspect can be handled. It is useful before an action when assigning a different scope or treatment; here the permission rules can be addressed apart from saved views.
다룰
'다룰' means 'to handle' or 'address' in 다룰 수 있습니다. It is the form of 다루다 used before the possibility construction and is useful for describing how a team will deal with an issue or feature.
개인용
'개인용' means 'for personal use' and modifies 버전 in 개인용 버전. It is useful before a product, feature, or version when limiting its intended use to an individual; here the customer says even a personal version would help.
버전만
'버전만' means 'only a version', with 만 restricting the requirement to that one version. The pattern noun plus 만 is useful for emphasizing a minimum condition; here the customer says a personal version alone would solve most of the problem.
있어도
'있어도' means 'even if there is one' or 'even with one available' in 개인용 버전만 있어도. It comes from 있다 with the concessive ending 어도, a useful pattern for saying that a result holds despite a limited condition.
제
'제' means 'my' and is the possessive form of 저, referring politely to the speaker's own problem. It is useful before a noun to identify personal ownership; here it identifies the customer's problem.
문제의
'문제의' means 'of the problem', with 의 linking 문제 to the following quantity expression. The noun-plus-의 pattern is useful for expressing a relationship such as possession or scope; here it specifies most of the speaker's problem.
대부분을
'대부분을' means 'most of' something as the object of 해결하다, with 을 marking the object. It is useful when describing a majority rather than the whole; here the personal version would address most, but not necessarily all, of the problem.
해결할
'해결할' means 'to solve' in 해결할 수 있을 것입니다. It is the form of 해결하다 used before the possibility expression, and it is useful for describing how a feature addresses a problem.
있을
'있을' contributes the possibility or expected availability in 해결할 수 있을 것입니다. It is the form of 있다 used before 것입니다, and the full expression is useful for making a formal projection about what the feature would make possible.
것입니다
'것입니다' gives the conclusion a formal explanatory ending in 있을 것입니다, meaning 'would be possible' in this context. It is useful when presenting an expected result or considered conclusion; here the customer explains the value of a limited first version.
그렇다면
'그렇다면' means 'then' or 'if that is the case' and connects the customer's point to the support representative's proposal. It is useful at the start of a response when accepting a premise and drawing a practical consequence.
첫
'첫' means 'first' and modifies 단계 in 첫 단계. It is useful before an ordered noun when identifying the initial item or phase; here it introduces the initial development focus.
단계에서는
'단계에서는' means 'in the step' or 'at the stage', with 에서 marking the scope and 는 setting it as the topic. The pattern is useful for describing what will happen during a particular phase; here the first step is limited to private saved views.
비공개
'비공개' means 'private' or 'not public' and modifies the saved views. It is useful in software contexts when access is not open for general sharing; here the proposed first version keeps views private.
저장
'저장' contributes the idea of saving or stored data in 저장 보기. It identifies the view as part of a saving feature and is useful in software terminology when discussing stored settings or views.
보기에
'보기에' marks the views as the target of focus in 보기에 초점을 맞출 수 있겠습니다. The pattern of a noun followed by 에 with 초점을 맞추다 is useful for stating what a plan or discussion will concentrate on; here the focus is private saved views.
초점을
'초점을' means 'the focus' as the object of the expression 초점을 맞출, with 을 marking that object. The reusable expression 초점을 맞추다 means to direct attention toward a target; here the target is private saved views.
맞출
'맞출' contributes the action of directing or setting focus in 초점을 맞출 수 있겠습니다. It is the form of 맞추다 used before the possibility phrase, and the pattern is useful when describing what a plan will concentrate on.
있겠습니다
'있겠습니다' completes 맞출 수 있겠습니다 and gives the formal tentative meaning 'could' or 'would be possible'. This form is useful when a support representative proposes a feasible next step; here the first step could focus on private saved views.
Grammar Points
동사-(으)면
필터를 계속 바꾸면 시간이 낭비됩니다.
FEEL-tuh-reul gyeh-sok bah-koo-myun shee-gahn-ee nang-bee-doem-nee-dah.If you keep changing the filter, time is wasted.
-(으)면 expresses a condition: when or if an action happens, a result follows.
동사-되다
시간이 낭비됩니다.
shee-gahn-ee nang-bee-DOEM-nee-dah.Time is wasted.
-되다 forms a passive expression, showing that the subject receives an action.
Korean Vocabulary
계속
adv
gyeh-SOK
repeatedly; continuously
대시보드
noun
dae-shee-BOH-duh
dashboard
방법
noun
bang-BOP
way; method
사용자
noun
sah-yong-jah
user
사용자 지정 보기
phrase
sah-yong-jah jee-jung BOH-gee
custom view
여러
det
YUH-ruh
several
요청했습니다
verb
yo-cheong-HAET-seum-nee-dah
requested
유지할
verb
yoo-JEE-hal
to keep; to maintain
저장할
verb
juh-JANG-hal
to save
주간 검토
phrase
joo-GAHN gum-toh
weekly review
평소 설정
phrase
pyung-soh SUHL-jung
usual setup
필터
noun
FEEL-tuh
filter
Quiz
Spelling
Tap the letters to spell the word.
requested
Show Answer
요청했습니다dashboard
Show Answer
대시보드filter
Show Answer
필터to keep; to maintain