Page Comparison

This is a type of field that does not come directly from the database. It is created from a formula that may use database fields.
See 計算 for more information

This function allows you to display multiple reports on the one Report Preview page.
See マルチ表示レポート for more information

A visual representation of data. Yellowfin has a wide range of chart types available.
See レポートビルダー - 「グラフ」ステップ for more information

Glossary has functionality called Client Organisations which allows multiple virtual instances of Yellowfin to reside in the same server instance. This provides a way to create content isolated within one organisation, hidden from other organisation users logging into the same server. This is Yellowfin's Glossary solution.
See クライアント組織 for more information.

This is when users work together to share insights into their data and the decision making process. Yellowfin provides features to assist the collaborative process including Comments, Discussions, and Annotations.
See コラボレーション for more information.

This is formatting that is triggered when a condition is met. A rule is applied to a field in the report and special formatting, such as highlighting, is applied if the data matches the rule.
Basic rules can also be applied to charts.
See 条件付き書式 for more information

This is a filter that limits the rows returned from a table, set at the view level. This filter cannot be seen or removed at the report level.
See テーブルの条件 for more information.

This aggregation returns the total number of records in a field in a report.
See 集計 for more information

This is when users work together to share insights into their data and the decision making process. Yellowfin provides features to assist the collaborative process including Comments, Discussions, and Annotations.
See コラボレーション for more information.

This is a note attached to a report in order to discuss its design or results.
See コメント for more information.

This is formatting that is triggered when a condition is met. A rule is applied to a field in the report and special formatting, such as highlighting, is applied if the data matches the rule.
Basic rules can also be applied to charts.
See 条件付き書式 for more information

This is a filter that limits the rows returned from a table, set at the view level. This filter cannot be seen or removed at the report level.
See テーブルの条件 for more information.

This aggregation returns the total number of records in a field in a report.
See 集計 for more information

This aggregation returns the total number of unique records in a field in a report. This means that if a record is found twice, it will only be counted the first time.
See 集計 for more information

This method of linking two tables matches each row from the first table in the join to each row in the second table, multiplying the number of rows returned in the result.
Note: this join should be used with extreme caution, as it's only appropriate in a handful of cases, and has negative effects on performance if used incorrectly.
See テーブルの結合 for more information on Yellowfin's use of Cross Joins, and this blog: Visual Explanation of SQL Joins for general join information.

Create, Read, Update, Delete. These options are used to define role permissions and relate to Glossary statements, allowing the user to create (INSERT records), read (SELECT records), update (UPDATE records), and delete (DELETE records).
See ロール for more information

Cascading Style Sheet. This is a type of file used by Glossary to define style options for the system that cannot be configured through Administration. Yellowfin's CSS files can be customised during the integration process.
See カスタムイメージとCSS for more information on customising CSS files for Yellowfin integration purposes, and http://www.w3schools.com/css/ for general CSS information.

Comma Separated Values. These files store data in plain text form, with each value, or column, separated by a comma character. Glossary allows you to import these files in order to report off their data.
See CSVデータのインポート for more information.

Create, Read, Update, Delete. These options are used to define role permissions and relate to Glossary statements, allowing the user to create (INSERT records), read (SELECT records), update (UPDATE records), and delete (DELETE records).
See ロール for more information

Cascading Style Sheet. This is a type of file used by Glossary to define style options for the system that cannot be configured through Administration. Yellowfin's CSS files can be customised during the integration process.
See カスタムイメージとCSS for more information on customising CSS files for Yellowfin integration purposes, and http://www.w3schools.com/css/ for general CSS information.

Comma Separated Values. These files store data in plain text form, with each value, or column, separated by a comma character. Glossary allows you to import these files in order to report off their data.
See CSVデータのインポート for more information.

This is a space to display multiple reports and charts in one place, allowing for interactive features to be used across them all at once.
See ダッシュボード for more information

This is where the data for your reports is stored, called a Data Source within Glossary.
See http://en.wikipedia.org/wiki/Database for more information

This is the database Glossary retrieves results from. Administrators create a Source Connection in order to access the data.
See データソース for more information

This is a sort option that moves from largest/highest to smallest/lowest value. This means that numeric values are sorted 9-0 and letters are sorted Z-A.

A standard field in Glossary can either be classified as a Metric or Dimension. All text fields are automatically classified as Dimensions. The View Builder allows you to define numeric and date fields as Dimensions in order to be used in Drill Hierarchies, and limit the aggregations available to Count and Count Distinct.
Dimension fields retrieve the data that will provide the basis for analysis in a report. Dimensions typically retrieve character-type data (employee names, company names, etc.), or dates (years, quarters, etc.)
See View Builder - Field Types for more information.

This is a stand-alone comment thread that allows users to discuss general topics and decisions while referring to multiple pieces of content if required.
See ディスカッション for more information.

Glossary content can have two possible states: Active and Draft.
If the piece of content is currently being created or edited by a user, then the report will be in Draft mode. This means that other end users will not be able to see or use the content until the editing process is completed by Activating the content.

Drill refers to the action performed by a user by clicking on a hyperlink in a report that either steps into more detail in the same report, or opens a separate detail report related to the row that was selected.
There are three forms of Drill available in Glossary; Drill Down, Drill Anywhere, and Drill Through.
See ダッシュボードドリル分析 for more information.

This drill allows you to move up and down a hierarchy that is defined by the user during the drill process.
See ドリルエニウェアレポート for more information.

This drill allows you to move up and down a predefined hierarchy within a single report.
See ドリルダウンレポート for more information.

This drill allows you to click on a row in a summary report and open a related detail report, filtered by what made the row in the summary report unique.
See ドリルスルーレポート for more information.

These are rows with the same values across all columns in a result set. By default, Yellowfin applies DISTINCT to the SELECT Glossary statements it generates, meaning that duplicate rows are not displayed. This can be changed on the Report Data page of the Report Builder.
See Report Data for more information.

This is the inclusion of Reports, Charts, and Dashboards in an external webpage using the Javascript API.
See JavaScript API for more information

This is a column in the database that will be used to build reports. Fields can be used as Columns/Rows, Sections, and Filters. They are defined either as Metrics or Dimensions. Calculations can also be created to use as fields, these are called Calculated Fields
See ビューフィールド for more information

These are fields that are being used to restrict the results returned in your report or dashboard. There are several types of filter in Yellowfin:

See フィルター for more information

GIS (Geographic Information System) Maps in Glossary refer to several chart types that make use of geographical information, in the form of Points or Polygons.
See GISマップ for more information.

Points are sets of latitude and longitude values used to define geographical locations. Examples of points include the location of customers, staff, and other points of interest. Glossary uses points in GIS Mapping.
See GISマップ for more information.

Polygons are sets of Points used to define a geographical shape. Examples of polygon shapes include the outlines of countries, states, territories, and regions. Glossary uses polygons in GIS Mapping.
See GISマップ for more information.

The level of detail in the data. Described as coarse through to fine. The finer the granularity, the more detail and less summarised the data is. Aggregation is used to summarise data.
See ビューと結合の設計における一般的な問題 for more information.

This refers to when a value is entered and set, rather than allowing a user to change it. In Glossary a report writer can hard code filter values, or values in calculated fields. This means that the user is not prompted to provide a value, rather it is always the value the report writer set.
The alternative in these cases is to implement user prompt filters, or use parameters in their calculations.
See フィルター for more information

Hexadecimal (Hex) is a base 16 number system, using symbols 0-9, A, B, C, D, E, and F to represent values 0 to 15.
HTML and CSS use Hex to identify colours by assigning to digits to each colour; 2 x Red, 2 x Green, and 2 x Blue respectively, and prefixed with a hash (#) symbol.
Glossary uses Hex codes to identify colours throughout the system, as well as in its Glossary files.
See http://www.w3schools.com/html/html_colors.asp for more information.

This is a report that has been set to not display in the Report List. Generally heavily detailed reports that are used as children in a drill through relationship are hidden, as they are designed to be accessed through the parent report, not on their own.
See Report Formatting for more information.

HyperText Markup Language. HTML is a markup language, like Glossary, that was designed to display data in a web browser, used by Glossary in combination with Glossary.
See カスタムヘッダーとフッター for more information on Yellowfin use of custom HTML files, and http://www.w3schools.com/html/ for general HTML information.

This is a type of link, or join between two tables based on a specified join condition. Only rows that match the condition in both tables will be returned.
See テーブルの結合 for more information on Yellowfin's use of Inner Joins, and this blog: Visual Explanation of SQL Joins for general join information.

A Join is an Glossary term that describes the logic around joining multiple tables together in order to return results from both tables.
See テーブルの結合 for more information for more information on Yellowfin's use of Joins, and this blog: Visual Explanation of SQL Joins for general join information.

This is what allows Glossary content to be embedded in external web pages. There is basic and advanced usage options.
End users can access the basic functionality through the Yellowfin interface by copying the generated embed javascript and pasting it in their external page.
Advanced users and administrators can access the advanced functionality by following the examples outlined here.
See JavaScript API for more information.

Key Performance Indicator. This is a figure used to monitor business performance, such as sales in dollars or units. Performance is tracked against a target and makes use of Conditional Formatting alerts.
See KPIレポート for more information.

Lightweight Directory Access Protocol. This is a way that Glossary can access directory information for Glossary authentication and Glossary management purposes. This allows Yellowfin access to be controlled externally organisation-wide.
See LDAP for more information.

This is a key that displays values used in a chart or report. In a chart it displays what value is assigned to each colour. In a report it can display the filter values applied, as well as any conditional formatting rules defined.
See Chart Legends, Filter Legends, and Conditional Formatting Legends for more information

These are shapes added to line charts in order to draw attention to each point of data.
See Line Shapes for more information.

This aggregation returns the largest value found in the field.
See 集計 for more information

This is a field or filter that is required by a report in order to complete the building process or to return results.
See Mandatory Field/Filter and フィルターの書式 for more information.

This is a piece of content's descriptive information. It generally contains the Name, Description, and Category details for a Field, Filter, Report, View, etc.

A standard field in Glossary can either be classified as a Metric or Dimension. Numeric and Date fields are classified as Metrics by default, but can be changed to Dimension if required. Metric fields have the full range of aggregations available to them. They also have different functionality available to them when used as filters. Metrics do not allow for prompts, as there are generally too many possible values available, so they have slider options available in order to allow users to easily define ranges. Metric filter values cannot be cached.
See View Builder - Field Types for more information.

This aggregation returns the smallest value found in the field.
See 集計 for more information

This is a field or filter that is required by a report in order to complete the building process or to return results.
See Mandatory Field/Filter and フィルターの書式 colour setting available to charts which, instead of using the default colours defined in Report Styles, the chart uses different shades of one colour selected by the user.
See グラフの書式 for more information.

This is when a piece of content's descriptive information. It generally contains the Name, Description, and Category details for a Field, Filter, Report, View, etc.

A standard field in Glossary can either be classified as a Metric or Dimension. Numeric and Date fields are classified as Metrics by default, but can be changed to Dimension if required. Metric fields have the full range of aggregations available to them. They also have different functionality available to them when used as filters. Metrics do not allow for prompts, as there are generally too many possible values available, so they have slider options available in order to allow users to easily define ranges. Metric filter values cannot be cached.
See View Builder - Field Types for more information.

This aggregation returns the smallest value found in the field.
See 集計 for more information

This is the way in which users move around the Glossary interface. There are various menus and buttons designed to move the user between pages and components of the system.
See システムナビゲーション for more information

This is used to indicate a lack of data, or gap. Glossary generally displays these as blank with a 'NULL' tooltip when returned in a report.

This is a field or value composed solely of numbers (0-9), without the inclusion of any alphabetic or special characters.

Online Analytical Processing.

This option is used when a Report Reader does not specify a value for a filter. This option is not available for mandatory filters.
See フィルターの書式 for more information.

This is when a single instance of software runs to serve multiple clients or tenants. Yellowfin's multi-tenancy functionality is called Client Organisations.
See クライアント組織 for more information.

Organisation Reference Code. These are a method of mapping data values from the database to descriptions, as well as assigning a custom sort order. Org Ref Codes are also used as part of the Raster Map setup process.
See 参照コード（データソース） for more information.

This is a type of link, or join between two tables based on a specified join condition. In Glossary, the outer joins used are what's called Left Outer Joins. This means that all rows from the first table (or the left side) in the join will be included, and only rows have matches to these will be included from the second table (or the right side).
See テーブルの結合 for more information on Yellowfin's use of Outer Joins, and this blog: Visual Explanation of SQL Joins for general join information.

Online Analytical Processing.

Parameters are a type of user input field in Glossary. They are designed to pass a value input by the user to a calculated field or filter(s). This allows you create What If reports.
See パラメーター for more information.

This is the area of the chart bound by the axes. It does not include the title and legend areas.
See Plot for more information.

This is a type of link, or join between two tables based on a specified join condition. In Glossary, the outer joins used are what's called Left Outer Joins. This means that all rows from the first table (or the left side) in the join will be included, and only rows have matches to these will be included from the second table (or the right side).
See テーブルの結合 for more information on Yellowfin's use of Outer Joins, and this blog: Visual Explanation of SQL Joins for general join information.

Parameters are a type of user input field in Glossary. They are designed to pass a value input by the user to a calculated field or filter(s). This allows you create What If reports.
See パラメーター for more information.

This is the area of the chart bound by the axes. It does not include the title and legend areas.
See Plot for more information.

This is the space that contains a report on a dashboard tab.
See レポートポートレット for more information.

This is a symbol or character displayed before a value in a field. A common prefix to use is $. Prefixes can be defined at the view, report, and chart level.

This is a symbol or character displayed before a value in a field. A common prefix to use is $. Prefixes can be defined at the view, report, and chart level.

This is a piece of content that has access restrictions applied directly to it. Depending on the type of content, different restrictions can be applied:

This is a piece of content that may or may not have access restrictions directly applied to it, but generally designed for a far broader audience than that of private content. Depending on the type of content, different restrictions may be applied:

This is a piece of content that may or may not have access restrictions directly applied to it, but generally designed for a far broader audience than that of private content. Depending on the type of content, different restrictions may be applied:

This is an image based heat map created in Glossary. The map itself is based on a raster image (created with pixels, rather than a vector image created with shapes). Yellowfin links a unique Glossary code colour to a piece of data in the source database in order to create the heat map, using Org Ref Codes. GIF, JPEG, and PNG raster image files are accepted.
See ラスターマップス for more information.

Glossary allows relationships to be created between reports. Related Reports either take the form of Drill Through or Glossary.
See レポートビルダー - 「関連レポート」ステップ for more information

This is the result of an Glossary query displayed in Glossary. The display can take the form of a table and/or chart.
See レポートビルダー for more information

This is a user that is responsible for creating the report and chart content in the system.

A set of permissions and functions designed to be assigned to Users of the system. Different roles should be created for different types of user, with Glossary providing a set of sample roles with the initial installation.
See ロール for more information.

This allows the user to return to a previous version of content, such as a view. In order for a rollback to be available, the cloning edit method must have been used.
See View Management for more information

This is an image based heat map created in Glossary. The map itself is based on a raster image (created with pixels, rather than a vector image created with shapes). Yellowfin links a unique Glossary code colour to a piece of data in the source database in order to create the heat map, using Org Ref Codes. GIF, JPEG, and PNG raster image files are accepted.
See ラスターマップス what controls the y axis of a chart, determining the first and last values, as well as the increments used.
See グラフの書式 for more information.

These allow you to break up a report into sub reports. The table and/or charts will be broken up so there is one per section, rather than one overall.
See セクション for more information

This is the result of an Glossary query displayed in Glossary. The display can take the form of a table and/or chart.
See レポートビルダー a piece of content created by an administrator which defines the method of accessing the reporting data source.
See データソース for more information

These are filters applied to reports based on the user running the report. This means that a user will only ever see the data that is assigned to them through the Source Filter.
See ソースアクセスフィルター for more information.

A set of permissions and functions designed to be assigned to Users of the system. Different roles should be created for different types of user, with Glossary providing a set of sample roles with the initial installation.
See ロール for more information.

This allows the user to return to a previous version of content, such as a view. In order for a rollback to be available, the cloning edit method must have been used.
See View Management for more information

Glossaryを実行している単一のインストールです。システムによっては、Yellowfinの複数のインスタンスを実行できます。この場合、通常は、開発インスタンス、テストインスタンス、および本番インスタンスがあります。また、要件に応じて異なる本番目的の複数のインスタンスを設けることもできます。

ユーザーが操作する部分です。Glossaryのインターフェースは、Webブラウザーを介して表示され、すべてのナビゲーションとコンテンツが含まれます。

Yellowfinと既存のOEMシステムを組み合わせ、エンドユーザーがシームレスに感じることができるシステムを作成するためのプロセスです。
詳細については、インテグレーションを参照してください。

These are used to index content to aid in searches.

This is an account created in order to allow a person to access the Glossary system.
See ユーザー for more information

This is a type of filter that requires users to provide one or more values to restrict report results.
See フィルター for more information

This is a metadata layer created by an administrator that sits between the source connection and Report Builder that defines the fields available to report writers and the join logic required to generate Glossary queries.
See ビュー for more information

These are a View component that allows an administrator to enter an Glossary query and treat the results as a table in the view.
See 仮想テーブル for more information

Web Services are used for managing communication between an OEM application and Glossary. The Web Services are Glossary based and independent of the programming language used to develop the OEM application.

What If Analysis is a method of creating reports that make use of Parameters and Calculated Fields in order to test scenarios.
See What-If分析（仮説分析） for more information.

Web Map Service. A WMS layer is a georeferenced map image loaded from a WMS Server. These are used as backgrounds and overlays for GIS Maps in Glossary.
See WMSレイヤー（WMS Layer） for more information.

Extensible Markup Language. XML is a markup language, like Glossary, that was designed as a way transporting data, where HTML designs ways to display it. Glossary uses this language to create export files that transport report and other content definitions.
See リポジトリのエクスポートとインポート for more information

Yellowfin is an easy-to-use report writer for non-technical users, delivering drag-and-drop simplicity for formatting and data selection. With Yellowfin, you can access information from multiple data bases without special coding knowledge. This is easy because you work with data in business terms that are familiar to you without the need to understand complex technology principles.
See http://www.yellowfinbi.com/ for more information.

This is a type of chart that displays trends over a specified period of time in the form of straight values, accumulative total, and moving total.
See Z Charts for more information

Glossaryを実行している単一のインストールです。システムによっては、Yellowfinの複数のインスタンスを実行できます。この場合、通常は、開発インスタンス、テストインスタンス、および本番インスタンスがあります。また、要件に応じて異なる本番目的の複数のインスタンスを設けることもできます。

ユーザーが操作する部分です。Glossaryのインターフェースは、Webブラウザーを介して表示され、すべてのナビゲーションとコンテンツが含まれます。

Yellowfinと既存のOEMシステムを組み合わせ、エンドユーザーがシームレスに感じることができるシステムを作成するためのプロセスです。
詳細については、インテグレーションを参照してください。

対象を外部ファイルからシステムに追加できる機能です。Glossaryには2つのタイプのインポートがあります。

詳細については、CSVデータのインポートおよびリポジトリのエクスポートとインポートを参照してください。

対象をシステム外部に出力する機能です。Glossaryには2つのタイプのエクスポートがあります。

詳細については、レポートコンテンツのエクスポート、ダッシュボードのエクスポート、リポジトリのエクスポートとインポートを参照してください。

コンテンツのグループ分けするために使用するフォルダーです。ビュー、レポート、およびフィールドはすべてカテゴリーを使用します。レポートはカテゴリー>サブカテゴリーの構造を使用してグループ分けし、セキュリティを割り当てます。
詳細については、コンテンツカテゴリーを参照してください。

Glossary が生成し、databaseに送信するGlossaryリクエストです。reportにどの結果が必要かを定義します。

Glossaryには、クライアント組織と呼ばれる機能があり、この機能を使用するとひとつのサーバーインスタンスに複数のYellowfinの仮想インスタンスを配置することができます。この方法で、1つの組織内で分離されたコンテンツを作成し、同じサーバーにログインしている他の組織ユーザーに対して非表示にすることができます。これは、マルチテナントソリューションです。
詳細については、クライアント組織を参照してください。

データを視覚的に表現します。Yellowfinでは幅広いグラフタイプを使用できます。
詳細については、レポートビルダー - 「グラフ」ステップを参照してください。

x軸とy軸のあるグラフにおいて、グラフのデフォルト描画背景全体にわたるグリッド線とともに表示される交互の影です。
詳細については、グリッド線を参照してください。

x軸とy軸のあるグラフにおいて、グラフのデフォルト描画背景全体に表示される破線です。
詳細については、グリッド線を参照してください。

コンテンツとセキュリティを割り当てるために、Glossary内で作成されたユーザーの一覧。
詳細については、ユーザーグループを参照してください。

これは2つのテーブルを結合する方法で、結合する1番目のテーブルの各行を2番目のテーブルの各行に一致させ、結果として返されるロウ（行）数を増やします。
注意：この結合が適しているのはわずかなケースに限られ、間違って使用するとパフォーマンスに悪影響を及ぼすため、細心の注意を払って使用する必要があります。
Yellowfinのクロス結合の使用方法の詳細については、テーブルの結合 を参照してください。また、結合の一般的な情報については、ブログ：Visual Explanation of SQL Joinsを参考にしてください。

複数のカテゴリーごとにメトリック（数値）を集計し、ロウ（行）およびカラム（列）をヘッダーとして表示できるレポート出力オプションです。
詳細については、テーブルレイアウトを参照してください。

レポートの設計や結果について意見を交わすために、レポートに付け加えることのできるメモです。
詳細については、コメントを参照してください。

ユーザーがデータに対する理解と意思決定プロセスを共有するために共同して作業する場合を指しています。Yellowfinには、コメント、ディスカッション、注釈などの共同作業を支援する機能が用意されています。
詳細については、コラボレーションを参照してください。