選單：資源管理

此選單僅對具有管理權限的使用者可見。

此頁面允許具有相應角色（經理和管理員）的使用者對現有資源進行更改或創建新資源。

資源管理表格

當首次打開「資源管理」頁面時，將顯示當前使用者有權更改的現有資源表格，包括該使用者創建的資源以及其他人邀請其管理的資源。關於「名稱」、「組織」、「類型」、「子類型」、「紀錄數量」、「最後修改時間」、「上次發布時間」和「下次發布時間」等欄位的詳細說明，請參閱公共資源表格。此外，「資源管理表格」還包含以下資源基本資訊欄位：

可見性 - 指定誰有權查看資源的類別。如果資源為「公開」，則所有使用者都能在首頁的公共資源表格中查看。如果資源為「私密」，則僅創建者、被邀請管理該資源的使用者以及具有管理員角色的使用者才能在「資源管理表格」中看到。關於邀請他人管理資源的詳細資訊，請參閱「資源管理」中「資源概覽」標題下「資源管理員」的部分。
作者 - 創建該資源的 IPT 使用者。

創建新資源

在「資源管理表格」下方有一個表單，可用於創建新資源。首先，需要為資源提供一個唯一的「短名稱」。該短名稱將用於在 IPT 實例中唯一標識該資源，並用於生成訪問資源的 URL。短名稱必須至少包含三個字元，可包含字母和數字（A-Z、a-z 和 0-9），但不得包含空白、破折號和底線以外的標點符號，或重音字元（例如，「firstresource」或「first_resource」，但不能是「first resource」或「première ressource!」）。其次，需要提供一個資源類型。請注意，當加載一個可選的 Darwin Core 存檔資源時（詳見下文），系統將自動確定並覆蓋此選擇的類型。第三，可以上傳可選的存檔資源。以下部分將描述可以衍生新資源的不同類型的存檔資源：

Darwin Core Archive or Camtrap Frictionless Data Package,
[上傳壓縮的（.zip）IPT 資源配置資料夾],
metadata file (EML or Frictionless metadata)

當然，您也可以選擇 完全創建一個新的資源，而不加載現有的存檔資源。在此選項中，資源的配置將需要通過 IPT 表單全部創建，包括上傳資料來源檔案（或連接到資料庫或 URLs）並將其中的欄位對照到適當延伸資料集中的術語。請注意，IPT 有 10GB 的檔案上傳限制，但是，IPT 匯出/發布的達爾文核心集檔案大小沒有限制。請參閱有關檔案上傳限制的說明以了解如何應對檔案上傳限制。

開始時，請先輸入新的資源簡稱，然後按下標有「創建」的按鈕。這將打開資源概覽頁面。接著，根據「選單：資源管理」部分中「資源概覽」標題下的說明，完成資源管理頁面的各個部分。

上傳達爾文核心集檔案

IPT 可以匯入大小高達 10GB 的達爾文核心集檔案。關於達爾文核心集檔案的資訊可以在 Darwin Core 網站找到，並且有更多關於 IPT 如何使用它們的說明請參考 xref.dwca-guide.adoc[此處]。要匯入達爾文核心集檔案，點選標有「選擇檔案」的按鈕來找到目標檔案。選擇檔案後，其名稱將顯示在「選擇檔案」按鈕旁。

點擊標有「創建」的按鈕。如果匯入檔案時發生問題，系統將顯示錯誤訊息通知使用者。如果匯入成功，將顯示資源概覽頁面，頁面頂部會有一則訊息說明匯入的結果。

上傳已壓縮的 IPT 資源配置資料夾

使用者可以從壓縮的 IPT 資源配置資料夾建立資源的副本，前提是該資源必須在相容的 IPT 版本下建立。這種方式將複製資源所有的詮釋資料、來源資料和資料對照，但不會複製其註冊資訊、版本歷史、DOI、版本號碼、管理者、發布狀態、建立日期、最後發布日期，也不會保留資源的簡稱。

操作步驟如下：

找到您要複製的資源配置資料夾。資源配置資料夾儲存在 $data-directory/resources 資料夾中，並使用資源簡稱命名。舉例來說，如果資源的簡稱是「ants」，則它將位於 $data-directory/resources/ants。
壓縮（打包）資源配置資料夾：ants/ → ants.zip
在「選單：資源管理」頁面的「創建新資源」部分中：
1. 輸入新的資源簡稱。如果壓縮資源的簡稱尚未在 IPT 中存在，則可以保留其簡稱。
2. 點擊標有「選擇檔案」的按鈕，然後找到並選擇已壓縮的目標資源配置資料夾。
3. 選擇檔案後，其名稱將顯示在「選擇檔案」按鈕旁。點擊標有「創建」的按鈕。如果匯入檔案時發生問題，系統將顯示錯誤訊息通知使用者。如果匯入成功，將顯示資源概覽頁面，並將該資源的詮釋資料、來源資料和資料對照從壓縮資源中複製到新的資源中。

上傳詮釋資料檔案

IPT 可以匯入和匯出符合「GBIF 詮釋資料設定檔」的有效資料集詮釋資料檔案。關於 GBIF EML 詮釋資料設定檔的資訊，以及如何撰寫符合 GBIF 達爾文核心標準詮釋資料設定檔的詮釋資料文件，請參考 GBIF 詮釋資料設定檔 - 使用指南。要匯入詮釋資料檔案，選擇資源類型「僅詮釋資料」，然後點擊標有「選擇檔案」的按鈕，找到並選擇目標詮釋資料檔案。選擇檔案後，其名稱將顯示在「選擇檔案」按鈕旁。

點擊標有「創建」的按鈕。如果匯入檔案時發生問題，系統將顯示錯誤訊息通知使用者。如果匯入成功，將顯示資源概覽頁面，其中詮釋資料也會顯示在畫面上。由於此為僅詮釋資料的資源，來源資料和對照的部分將保持隱藏。如果您稍後決定新增原始資料集，只需在詮釋資料的 [基本詮釋資料] 頁面中更改資源類型。

編輯現有的資源

現有資源表僅顯示當前使用者可以編輯的資源。要編輯資源，請在資源表中點擊資源名稱。該連結將打開所選資源的資源概覽頁面。請參考「選單：資源管理」部分中「資源概覽」標題下的說明，以了解如何編輯該資源的各種相關資料。

資源概覽

此頁面允許具有管理許可權的使用者編輯資源配置。資源名稱顯示在頁面頂部的選單列下方。如果資源尚未命名，則會在頁面頂部顯示資源簡稱，並充當標題。資源名稱下方是一個表格，左側顯示資源配置的各個類別，右側顯示相應的區段。表格中的資訊圖示可幫助引導管理者去使用各類別。這些類別各自的配置方式將在後續部分詳細說明。

來源資料

資源概覽頁面的此區域允許使用者從檔案、資料庫或 URL 匯入原始資料到 IPT。如果資源沒有來源資料，則被視為僅詮釋資料資源，即僅包含資料集的資訊，無任何原始資料。如果多個資料來源彼此相關，也可以將資源連結到多個資料來源。更多關於多個資料來源之間的關聯說明，請參閱達爾文核心標準文字檔指南的實作指南部分。以下是選擇來源資料的初步步驟說明，無論是來自文字檔、資料庫來源或可用於 URL 的文字檔：

檔案作為資料來源

IPT 可以匯入未壓縮的分隔文字檔（如 CSV、Tab，或使用其他分隔符的檔案）或以 Zip 或 Gzip 壓縮的等效檔案，也支援 Excel 檔案。點擊「來源資料」的 ┇ 選單，選擇「添加」，然後在彈出視窗中從下拉框中選擇「檔案」，並點擊標有「瀏覽…」或「選擇檔案」的按鈕來尋找並選擇要匯入的檔案。檔案名稱僅能由字母數字字符（A-Z、0-9）、空格、底線、句號、括號和連字符組成。選擇檔案後，其名稱將顯示在「瀏覽…」按鈕的右側。

點擊標有「清除」的按鈕以移除所選檔案，並返回到選擇來源資料之前的狀態。或者，點擊標有「添加」的按鈕以打開來源資料檔案詳細頁面（如果存在同名檔案覆寫風險，系統將顯示對話框，詢問使用者是否確認覆寫）。

如果 IPT 檢測到在覆寫時已經對照的資料來源中的欄位數已更改，系統將警告使用者應更新其資料對照。

上傳大小限制

IPT 的上傳大小限制為 10GB。對於匯出/發布的達爾文核心集檔案，IPT 則無大小限制。若要將超過 10GB 的資料集載入 IPT，建議採用以下解決方案：

使用 Zip 或 Gzip 壓縮檔案
將資料載入 IPT 支援的 IPT 支援的資料庫之一
從 URL 檢索檔案
拆分檔案（當資料集發布時，IPT 將按照映射順序合併檔案）

此頁面顯示資源名稱以及檔案特徵摘要（可讀性、檢測到的欄數、檔案的絕對路徑、檔案大小、檢測到的行數和檔案最後載入到 IPT 的日期）。來源資料檔案詳細頁面允許使用者檢視並編輯描述所選檔案內容的參數，並使用這些設置來分析和預覽檔案。

來源名稱 - 標頭，選定檔案的名稱，不包括副檔名。
來源類型 - 來源的類型，此處為文字檔。
可讀 - 此圖示表示資料是否可使用此頁面上所提供的檔案格式資訊。
檔案 - 用於作為資料來源的檔案完整路徑。
欄位數 - - 依照此頁面設定的參數，資料集中的欄位數。
行列數 - 資料檔案中找到的行列數。（註：此數字有助於確認所有紀錄是否已被識別。）
檔案大小 - 資料來源檔案的大小。
最後修改 - 檔案最後儲存的日期戳記。
來源紀錄 - 此連結下載處理檔案時所產生的紀錄檔案，記錄了此頁面的資訊。任何處理過程中遇到的問題，例如遺失的資料或意外格式，將會顯示在此紀錄檔案中。
分析 - （在選項下拉選單中）按此按鈕以根據此頁面的檔案設定生成資料摘要。分析會顯示檔案是否可讀，若可讀，則顯示欄位數。
預覽 - （在選項下拉選單中）按此按鈕以檢視檔案中的資料解釋。
標頭列數 - 若檔案不包含欄位名稱列則為 0，若包含欄位名稱列則為 1。
欄位分隔符 - 資料欄位之間分隔的字符或字符組合。
欄位引號 - 用來標示資料欄位起始的單一字符（或無），例如 ' 或 "。請注意，若欄位內容包含換行符號（\n）或回車符號（\r），則無法正確地標示欄位內容的起始。
複數值分隔符 - 用來分隔擁有多於一個值的欄位的單一字符（例如 | 或 ;）。
字元位元系統 - 定義資料中字元的位元系統（例如 ISO 8859-5 指的是西里爾字母）。
日期格式 - 用於描述具有日期型別的欄位格式的代碼（例如 YYYY-MM-DD 表示四位數年份、兩位數月份和兩位數日期，以短橫分隔）。
已選工作表 - （僅適用於 Excel 檔案）此下拉選單列出 Excel 檔案/活頁簿中所有工作表的名稱。僅可使用 1 張工作表作為資料來源，默認為第一張工作表。更改工作表後，點擊 Analyse 以更新行/列資訊。

設定好資料來源的參數以確保檔案正確解讀後，點擊標示「儲存」的按鈕以儲存此設定。如果儲存成功，將顯示「資源概述」頁面，並在此頁面上顯示該檔案的摘要資訊。要重新開啟「來源資料檔案」的相關細節頁面，只需點擊相關項目。

若使用者想要刪除此來源，他們可以重新開啟「來源資料檔案」的相關細節頁面，然後按「刪除來源檔案」按鈕。需注意，任何與此檔案相關的資料對照也會被刪除。

若來源資料包含多個文字檔，則可以對每個要匯入的檔案重複執行此部分描述的過程。也可以匯入包含多個文字檔的壓縮資料夾，以一次性新增多個來源檔案。

資料庫作為資料來源

IPT 可以使用資料庫連接來從表格或檢視表中匯入資料。受支援的資料庫連接列表請參見受支援的資料庫一節。要設定資料庫作為資料來源，點擊 ┇ 選單並選擇「新增」。然後從彈出視窗的下拉選單中選擇「資料庫」，再點擊標示「連接」的按鈕，這將打開「來源資料庫」的相關細節頁面。

「來源資料資料庫」的相關細節頁面顯示了資源名稱及資料庫特徵摘要（可讀性、偵測到的欄位數），並允許使用者查看及編輯如何從資料庫訪問資料的參數，以及使用這些設定來分析和預覽資料。

若 IPT 偵測到資料對照的來源資料中欄位數在編輯時發生了變化，系統會提醒使用者將其更新。

來源名稱 - 標頭，資料來源的名稱。與檔案資料來源不同，使用者可以編輯並任意命名此名稱。
來源類別 - 資料來源的類別，此處為 SQL。
可讀性 - 此圖示指示資料是否可使用此頁面上提供的連接資訊訪問。
分析 - （在選項下拉選單中）按此按鈕以根據此頁面的資料庫連接設定生成資料摘要。分析報告會顯示資料庫是否可讀，若可讀，則顯示 SQL 語句結果中的欄位數。
預覽 - （在選項下拉選單中）按此按鈕以根據此頁面的資料庫連接設定來檢視詮釋資料的內容。
資料庫系統 - IPT 必須連接以檢索資料的關聯式資料庫管理系統。
資料庫主機 - 資料庫伺服器地址，可選擇包含非預設埠號（例如 localhost 或 mysql.example.org:1336）。對於 ODBC 連接，不需要此項。
資料庫 - 資料庫管理系統中的資料庫名稱，或 ODBC 連接的 DSN。
資料庫使用者 - 連接資料庫時使用的資料庫使用者名稱。
資料庫密碼 - 連接資料庫的資料庫使用者密碼。
* SQL 語句* - 用來從資料來源資料庫中讀取資料的結構化查詢語言（SQL）語句。語句將依原樣傳送至已設定的資料庫，因此可以使用資料庫的任何原生功能，如函數、分組語句、限制語句或聯集語句（如果支援）。例如：SELECT * FROM specimen JOIN taxon ON taxon_fk = taxon.id。測試大型的來源資料時，建議在 SELECT 語句中加入相應語句以限制查詢返回的行數，例如在 MySQL 中 SELECT * FROM specimen JOIN taxon ON taxon_fk = taxon.id LIMIT 10。當語句已經過與達爾文核心資料對照的完整測試後（參見以下章節），使用者可以將 SQL 語句更改為回傳完整的資料集。
字元位元系統 - 定義資料中字元位元的系統（例如 Latin1、UTF-8）。
日期格式 - 用於描述具有日期型別的欄位格式的代碼（例如 YYYY-MM-DD 表示四位數年份、兩位數月份和兩位數日期，以短橫分隔）。
複數值分隔符 - 用來分隔擁有多於一個值的欄位的單一字符（例如 | 或 ;）。

當來源資料的參數設定完成並可以正確訪問資料後，點擊標示「儲存」的按鈕以儲存此配置。若儲存成功，將顯示「資源概述」頁面，並在來源資料區塊右側顯示資料的摘要資訊。來源資料摘要資訊中還會顯示一個標示「編輯」的按鈕，允許使用者重新開啟「來源資料庫」的相關細節頁面。

URL 作為來源資料

IPT 可以直接從 URL 匯入未壓縮的分隔文字檔案（CSV、tab 檔或其他分隔符號檔案）或壓縮檔案。點擊 ┇ 選單並選擇「新增」。接著，從來源資料類型的下拉選單中選擇「URL」，然後提供來源的名稱和類型，或直接將完整 URL（包括 http:// 或 https://）貼入下方的框中。

點擊標示為「清除」的按鈕可移除 URL 選擇並回到選取資料來源前的狀態。或者，點擊標示為「新增」的按鈕來開啟來源資料 URL 的相關細節頁面。

此頁面顯示資源名稱和 URL 特徵的摘要（可讀性、檢測到的欄數、URL 位置、檢測到的行數以及 URL 最後載入 IPT 的日期）。來源資料 URL 的相關細節頁面允許使用者查看和編輯描述所選檔案內容的設定參數，並使用這些設定進行分析和預覽。

從這裡開始的流程與使用檔案作為資料來源的方式非常相似。詳情請參閱檔案作為資料來源章節。

達爾文核心標準資料對照

資源概覽頁面的此部分允許使用者將傳入資料中的欄位對照到已安裝擴展中的欄位，並查看哪些來源欄位尚未進行對照。此選項僅在至少一個資料來源成功新增，且至少一個延伸資料集已安裝後才可用。

當滿足這些條件後，該下拉列表將包含一個選擇框，列出已安裝的核心類型和延伸資料集。選擇一個核心類型並進行對照，然後選擇要對照的延伸資料集。選擇與來源資料欄位相符的延伸資料集。如果在選擇框中沒有出現所需的核心類型或延伸資料集，則需要先安裝該延伸資料集。詳情請參閱「選單：系統管理」章節中的「設定核心類型和延伸資料集」標題下的說明。

選擇所需的核心類型或延伸資料集後，點擊標示為「新增」的按鈕以開啟資料來源選擇頁面。

資料來源選擇頁面

此頁面說明延伸資料集支援的資料類型，並顯示一個包含所有已配置的資料來源的選擇框。

一個資源只能使用一種核心類型：當資源以分類單元名稱為基礎時，選擇「達爾文核心標準清單」；當資源以自然界中的出現紀錄（觀測紀錄）或收藏品（標本）為基礎時，選擇「達爾文核心標準出現紀錄」。只有在所需的核心類型完成對照後，才可以對照其他延伸資料集。

使用者可以將不同於該核心類型的其他核心類型作為延伸資料集進行對照。

選擇要對照的資料來源，然後點擊標示為「儲存」的按鈕以開啟資料對照的相關細節頁面（請跳轉到下文的 [資料對照相關細節] 以獲取實際進行對照的說明）。

新增對照後，它將顯示在「達爾文核心標準資料對照」。此區域會列出所有資源的對照，分為核心類型資料對照和延伸集資料對照。點擊任一項目以修改它，或點擊 ┇ 選單並選擇「預覽」來預覽當前的資料對照。建議資源管理者在發布新版本前預覽所有資料對照。

資料對照細節頁面

在建立資料來源與核心類型或延伸資料集的資料對照後，這個頁面將開啟並顯示從來源資料自動對照到延伸資料集欄位的欄位數量。轉換為小寫後的欄位名稱如果相符，則欄位會自動進行對照。

資料對照頁面允許使用者基於所選擇的延伸資料集指定此 IPT 資源中的資料配置方式。頁面頂部描述了來源資料被對照到的延伸資料集。來源資料的名稱是一個返回到編輯來源資料頁面的連結，延伸資料集的名稱是指向延伸資料集說明的連結。

A sidebar on the left-hand side of the page has links to jump to specific sets of related fields (classes/groups) in the extension plus filters to show and hide fields on the page.

To the right of the sidebar are rows of information divided into two columns of information; the first column (left-hand side) lists the names of fields in the extension; the second column (right-hand side) contains a set of controls (select boxes, text boxes) to set the value the extension field is supposed to contain. If a field name has been chosen in the source data field select box, text labelled "Source Sample" and a button labelled "Translate" will appear below it. Descriptions of the controls that may appear in the right-hand column of the data mapping table are given below:

Data source field select box - The left-hand select box is either blank or contains the name of a field from the data source. The IPT fills as many selections as it can from extension field names that match a data source field name. All of the remaining source field select boxes are left blank, signifying that the extension field has not been mapped to a source data field. If a field name is selected, the resource will use the value from that field in the source data as the value for the extension field in the Darwin Core Archive created by the IPT when the resource is published.
Data source field select box - ID field - This field can be matched to a source data field, or it can be set to "No ID" signifying that the field will not be mapped to a source data field. The ID field is required in order to link records from the two sources together. The ID can be auto-generated from the "Line Number" or "UUID Generator", but this feature is exclusively available when mapping a source to the Taxon Core Type’s taxonID field.
Constant value text box - To set the published value of any non-identifier extension field to a single value for every record in the data source, enter the desired constant for the extension field in the text box to the right of the source field select box. To activate the text box, make sure that no value is selected in the source field select box. Example:

Constant controlled value select box - If the right-hand column for the extension field contains a second select box instead of a text box, this means that the field is governed by a controlled vocabulary. In this case, choose a value from the vocabulary list to use as a constant value in place of typing a constant into a text box.

Use resource DOI - (Special constant controlled value) It is possible to set the default value for datasetID equal to the resource DOI. This option only applies to extensions having the Darwin Core term datasetID, such as the Occurrence extension. To activate the checkbox, make sure that no source data field has been selected and no constant value has been entered.

Vocabulary detail button - Extension fields that are governed by a controlled vocabulary will have an icon beside the controlled value select box. Click on this icon to open a Vocabulary detail page in a new browser tab on which is a list of accepted values for the extension field with explanations and alternative synonyms in various languages.
Source Sample - This area shows actual values from the first five records of the selected field of the source data, separated by spaces and the character |. This helps the user understand if the contents of the source data field are appropriate for the extension field to which it has been mapped.

Translate - Click on this button to open a Value Translation page on which distinct values in the selected field of the source data can be translated to new values in the archive generated by the IPT for this data resource. After the translations have been entered and saved, the Data Mapping page will appear again, and will display text as a link in place of the "Translate" button to show the number of values for which there are translations having values different from the original values. Click on this link to reopen the Value Translation page for this extension field.
Filter - The filter allows the user to include only records that match a criterion set for one of the source data fields. To use the filter, first select from the drop down whether you want the filter to be applied After Translation or Before Translation (in other words, after translations on the source data have been applied, or before - refer to Translation section above for more details about translation). Then, choose the field upon which the criterion will be based using the left select box. The text box at the right may contain a value against which to compare the value of the field in the source data. Do not enclose the value with any punctuation. The second select box allows the user to choose a comparison operator from among the following:
- IsNull - this operator is true if the source data field is empty. In this case no value is needed in the text box at the right. If there is a value in the text box, it will be ignored.
- IsNotNull - this operator is true if the source data field is not empty. In this case no value is needed in the text box at the right. If there is a value in the text box, it will be ignored.
- Equals - this operator is true if the source data field is equal to the value in the text box at the right. Equality is evaluated based on string matching, thus, if the data source value for a record is 2.0 and the value in the text box is 2, the record will not be included in the filtered data set.
- NotEquals - this operator is true if the source data field is not equal to the value in the text box at the right. Equality is evaluated based on string matching, thus, if the data source value for a record is 2.0 and the value in the text box is 2, the record will be included in the filtered data set.
Required fields - If there are any required properties that must be mapped for the Core Type or Extension, these have their names highlighted. Be aware basisOfRecord publication will fail if basisOfRecord has not been mapped for the Occurrence core. Also, a special case exists for the ID field, which is only required when linking two sources together.

In addition to the explanatory information about the extension at the top of the page and the two columns described above, the Data Mapping page may have following sections, links, and buttons:

Resource Title - clicking on this link will navigate to the Resource Overview page without saving any of the pending changes.
Hide unmapped Fields - this filter/link will remove from view on this page all fields that have not yet been mapped, leaving only those with completed mappings. To view again those fields that have not been mapped, click on the "Show all" link.
Show all fields - this filter/link will make all fields visible, whether mapped already or not. This link appears only after the "Hide Unmapped Fields" link has been invoked.
Hide redundant classes - this filter/link will remove from view on this page all fields belonging to classes/groups of terms that are redundant. A class is redundant, if it is already included in the core extension. To view again those fields that belong to redundant classes, click on the "Show all classes" link. This link appears only after the "Show all classes" link has been invoked.
Show all classes - this filter/link will make all fields belonging to redundant classes/groups visible. This link appears only after the "Hide redundant classes" link has been invoked.
Save - clicking on any of the potentially many buttons labelled "Save" will change the pending changes on the page.
Delete - clicking this button will remove the entire mapping to a data source, not just the mapped fields, and return to the Resource Overview page.
Back - clicking on this button will abandon all changes that have been made on this page since it was last saved and return to the Resource Overview page.
Unmapped columns - this section contains a list of columns in the source file, table, or view that have not been mapped. This list can help to determine if everything from the source has been mapped that should be mapped.
Redundant term classes - this section contains a list of classes whose terms are redundant, meaning that these classes already appear in the core extension. Ideally, a term that has been mapped in the core extension doesn’t need to be re-mapped again in an extension. Hiding redundant terms also has the additional benefit of making the mapping page easier to use for the user.

Value Translation page

When this page opens for the first time it shows a message at the top giving the number of distinct values of the selected field in the source data, up to 1000 values. The page shows the name and description of the extension field for which translations are being made. If the field is governed by a controlled vocabulary, information about that vocabulary and an icon to open a Vocabulary Detail page (see Vocabulary Detail button explanation, above) will appear under the field description. Below the field description is a table showing the distinct values of the field found in the source data under the column heading "Source Value" with text boxes under the column heading "Translated Value". Enter the value to which the Source Value should be translated in the text box. The icon to the left of the translated value text box indicates if the value provided exists in the vocabulary for this term.

Bounding the table above and below by the following set of buttons:

Save - click on this button to save all of the changes that have been made on this page and return to the Data Mapping page.
Delete - (from Options dropdown) click on this button to remove all translations for this field and return to the Data Mapping page.
Reload - (from Options dropdown) click on this button to search the source data again for distinct values. Existing translations are retained, and any new distinct values from the source data appear on the list without a translation.
Automap - (from Options dropdown) this button appears only if the field is governed by a controlled vocabulary. Click on this button to fill the Translated Values automatically with standard values based on known synonyms. Values in the source data for which there are no known synonyms will remain blank.
Cancel - click on this button to close the Value Translation page without saving any of the changes that have been made.

Vocabulary detail page

This page shows a list of concepts within the vocabulary. In the context of mapping data, it shows a list of accepted values that can be used for the extension field. Each concept may contain a description, its preferred synonyms (in various languages), plus any alternative synonyms (in various languages).

元數據

This area of the Resource Overview page allows a user to edit the resource metadata. To do this, click on the ┇ menu and select "Edit" in the dropdown. Every resource requires a minimal set of descriptive metadata in order to be published in the GBIF network, and if necessary assigned a DOI by GBIF. If any of the required metadata is missing, the Resource Overview page will open with a badge "Incomplete" in the Metadata area of the page.

An existing resource file can be uploaded, replacing any existing metadata. To do this, click the ┇ menu and select "Upload". Then click the "Browse" button and choose the EML file.

Clicking on the "Edit" option opens the [Basic Metadata] page, the first of a series of metadata pages. Each page will appear in sequence as the button labelled "Save" is clicked upon finishing entering data on any given metadata page. Saving the metadata on the last of the metadata pages will transition back to the [Basic Metadata] page. Clicking on the button labelled "Cancel" on any given metadata page will disregard any changes made on that page and return to the Resource Overview page. In a column at the left of each metadata page is a list of links to all of the metadata pages for easy reference and navigation. Click on any of the links to open the metadata page for that topic.

Following is a list of the metadata pages and their contents:

基本元數據

All metadata fields on this page are required. Please note for each contact you must supply at least a last name, a position or an organization.

Title - the Title for the resource. This title will appear as the name of the resource throughout the IPT. The title will also appear in the GBIF Registry, and form part of the citation. Please use a descriptive title for users of the dataset. "Aves Tanzanian collection at the Natural History Museum of Denmark (SNM)" is a good title, "aves_tz_snm" is not! Avoid using filenames or acronyms known only within your organization.
Publishing Organization - the organization responsible for publishing (producing, releasing, holding) this resource. It will be used as the resource’s rights holder and publishing organization when registering this resource with GBIF and when submitting metadata during DOI registrations. It will also be used to auto-generate the citation for the resource (if auto-generation is turned on), so consider the prominence of the role. If the desired organization does not appear in the list it may be added by the IPT Administrator (see the information under the "Configure Organizations" heading in the "Administration Menu" section). Please be aware your selection cannot be changed after the resource has been either registered with GBIF or assigned a DOI.
Update Frequency - the frequency with which changes are made to the resource after the initial resource has been published. For convenience, its value will default to the auto-publishing interval (if auto-publishing has been turned on), however, it can always be overridden later. Please note a description of the maintenance frequency of the resource can also be entered on the Additional Metadata page.
Type - the type of resource. The value of this field depends on the core mapping of the resource and is no longer editable if the Darwin Core mapping has already been made. If a desired type is not found in the list, the field "other" can be selected. Review the information under the "Configure Core Types and Extensions" heading of the "Administration Menu" section.
Subtype - the subtype of the resource. The options for this field depend on the Type field. If a desired subtype is not found in the list, the field can be left with the default selection.
Metadata Language - the language in which the metadata are written.
Resource Language - the language in which the data for the resource are written.
Data License - the licence that you apply to the resource. The license provides a standardized way to define appropriate uses of your work. GBIF encourages publishers to adopt the least restrictive licence possible from among three (default) machine-readable options (CC0 1.0, CC-BY 4.0 or CC-BY-NC 4.0) to encourage the widest possible use and application of data. Learn more about GBIF’s policy here. If you feel unable to select one of the three options, please contact the GBIF Secretariat at participation@gbif.org. To find out how to apply a license at the record-level, refer to the How To Apply a License To a Dataset section. To find out how to change the IPT’s default set of licenses, refer to the Applying a License to a Dataset page in the IPT wiki.
Description - a brief overview of the resource broken into paragraphs. This should provide enough information to help potential users of the data to understand if it may be of interest.
Resource Contacts - the list of people and organizations that should be contacted to get more information about the resource, that curate the resource or to whom putative problems with the resource or its data should be addressed. The contacts in the list can be rearranged by simply dragging the elements and placing them in the right place.
- Copy from another - click on this link to copy contact data from any resource. A modal window is displayed with options to choose the resource and the contact.
- Add new resource contact - click on this link to initiate a form for an additional resource contact.
- Remove this resource contact - click on this link to remove the resource contact that follows immediately below the link.
- First Name - the first or given name of the resource contact.
- Last Name (required if Position and Organization are empty, required if the first name is not empty) - the last or surname of the resource contact.
- Position (required if Last Name and Organization are empty) - the relevant title or position held by the resource contact.
- Organization (required if Last Name and Position are empty) - the organization or institution with which the resource contact is associated. Though the organization may be one of those registered in the GBIF Registry, this is not required. Thus, the organization must be entered in the text box rather than selected from a list of registered organizations.
- Address - the physical street or building address of the resource contact.
- City - the city, town, municipality or similar physical location of the resource contact’s address.
- State/Province - the state, province, or similar geographic region of the resource contact’s address.
- Country - the name of the country or other first level administrative region of the resource contact’s address.
- Postal Code - the postal code (e.g., zip code) of the resource contact’s address.
- Phone - the preferred full international telephone number at which to reach the resource contact.
- Email - the preferred email address at which to reach the resource contact.
- Home Page - the URL to a worldwide web page for the resource contact.
- Personnel Directory - the URL of the personnel directory system to which the personnel identifier belongs. There are four default directories to choose from: ORCID, ResearchID, LinkedIn, and Google Scholar. If you’d like to change the IPT’s default set of directories, refer to the Add a New User ID Directory page in the IPT wiki.
- Personnel Identifier - a 16-digit ORCID ID (e.g. 0000-0002-1825-0097) or another identifier that links this person to the personnel directory specified.

Resource Creators - the people and organizations who created the resource, in priority order. The list will be used to auto-generate the resource citation (if auto-generation is turned on). If this person or organization is the same as the first resource contact, all of the details of the latter can be copied into the equivalent fields for the resource creator by clicking on the link labelled "copy details from resource contact". The resource creator has all of the same fields and requirements as the resource contact. Refer to the field explanations under Resource Contacts, above.

the person(s) or organization(s) responsible for the creation of the resource as it appears in the IPT and for effectively publishing the resource can add themselves as an associated party with role 'publisher'.

Metadata Providers - the people and organizations responsible for producing the resource metadata. If this person or organization is the same as the first resource contact, all of the details of the latter can be copied into the equivalent fields for the resource creator by clicking on the link labelled "copy details from resource contact". The metadata provider has all of the same fields and requirements as the resource contact. Refer to the field explanations under Resource Contacts, above.

地理涵蓋範圍

This metadata page contains information about the geographic area covered by the resource. The page contains a map and associated controls that allow the user to set the geographic coverage. Below is a screen image showing the contents of the Geographic Coverage page, followed by explanations of the controls.

IPTManageResourceMetadataGeographicCoverage

Automatically infer from source data - source data would be analyzed and the geographical coverage would be set automatically on publication.
Preview inferred - analyze source data and display inferred values.
Coverage Map - if connected to the Internet, a map of the earth will appear on the geographic coverage page. This map shows a box with control points (markers) on all corners. The corners correspond with the values in the Latitude and Longitude text boxes, explained below. Drag the entire box, or drag individual markers to a new location to reset the geographic bounds of the box. The corresponding latitude and longitude values will change to match the box on the map. The map features hill shading, natural vegetation colours, advanced labelling, etc. The map has buttons to zoom in (+) and zoom out (-) and can be dragged in any direction to change the area of the earth being shown.
Set global coverage? - click on this check box to change the geographic coverage to cover the entire earth.
South/West & North/East - these four text boxes correspond to the SW and NE corners of the box bounding the area covered by the resource. The values to enter in these text boxes are decimal degrees (e.g. 45.2345), with the standard limiting values of -90 to +90 latitude (South/North) and -180 to +180 longitude (West/East), with positive latitude in the northern hemisphere and positive longitude east of the Greenwich Meridian to the International Dateline. Manipulating the bounding box markers on the map will set these values, but valid values can all be entered in these text boxes directly if desired. The map will update when the information on the page is saved by clicking on the button labelled "Save".
Description - a textual description of the geographic coverage. This information can be provided in place of, or to augment the information in the other fields on the page.

分類群涵蓋範圍

This metadata page allows the user to enter information about one of more groups of taxa covered by the resource, each of which is called a taxonomic coverage. Each coverage consists of a description and list of taxa, where each taxon consists of a taxon name (either scientific or common) and a taxon rank. Before any taxonomic coverages are created, the page shows only a link labelled "Add new taxonomic coverage". Clicking on this link will show a text box for the description and several links. Below is a screen image showing the Taxonomic Coverage page before any data have been entered, followed by explanations of the controls seen on the page in this state.

Automatically infer from source data - source data would be analyzed and the taxonomic coverage would be set automatically on publication.
Preview inferred - analyze source data and display inferred values.
Remove this taxonomic coverage - click on this link to remove the taxonomic coverage that follows immediately below the link, including the description, the list, and all single taxon entries.
Description - a textual description of a range of taxa represented in the resource. Each taxonomic coverage has its own description. This information can be provided in place of, or to augment the information in the other fields on the page.
Add several taxa - this link adds a text box labelled "Taxon List" to the page.

Taxon List - this text box allows the user to enter a list of taxa with each taxon on a separate line by using the ENTER key within the text box. The taxa entered in this list are treated as scientific names.
Add - this button processes the values entered in the Taxon List text box and creates scientific names for each of them within the taxonomic coverage.
Add new taxon - this link adds controls to enter a single taxon to the taxonomic coverage - text boxes for Scientific Name and Common Name, a select box for Rank and a "Remove this taxon" link. The taxon can contain any combination of scientific and common name with an optional rank.

Scientific Name - this text box is meant to contain the scientific name for the taxon.
Common Name - this text box is meant to contain the scientific name for the taxon.
Rank - this text box is meant to contain the taxonomic rank of the taxon.
Remove this taxon - clicking on this link will remove the taxon (scientific name, common name, and rank) to the left of the icon from the taxonomic coverage.
Add new taxonomic coverage - click on this link to initiate a form for a new taxonomic coverage with a text box labelled "Description" and links to "Add several taxa" and "Add new taxon" as described above.

時間涵蓋範圍

This metadata page contains information about one of more dates, date ranges, or named periods of time covered by the resource, each of which is called a temporal coverage. Coverages may refer to the times during which the collection or data set was assembled (Single Date, Date Range, and Formation Period), or to times during which the subjects of the data set or collection were alive (Living Time Period). Before the first temporal coverage for the resource is created, the page shows only a link labelled "Add new temporal coverage". Clicking on this link will show the default temporal coverage type "Single Date" in a select box, a text box labelled "Start Date", a calendar icon, and two links. Below is a screen image showing the default Temporal Coverage page before any data have been entered, followed by explanations of the controls seen on the page in this state.

IPTManageResourceMetadataTemporalCoverages

Automatically infer from source data - source data would be analyzed and the temporal coverage would be set automatically on publication.
Preview inferred - analyze source data and display inferred values.
Add new temporal coverage - click on this link to initiate a form for an additional temporal coverage.
Remove this temporal coverage - click on this link to remove the temporal coverage that follows immediately below the link.
Temporal Coverage Type - select one of the options in this select box to set the type of temporal coverage, which can consist of a single date, a date range, a formation period, or a living time period. Selecting a type will reveal controls appropriate to the choice as explained below.
- Single Date - this is the default temporal coverage type showing when a temporal coverage is first created. This type is meant to represent a coverage spanning one day. Selecting this type reveals a text box for a Start Date, with a calendar icon to the right with which a date can be selected.
  - Start Date - this text box is meant to contain a single date in one of the supported date formats. To select a date, click on the calendar icon and choose a date, or enter the date manually. To find out what date formats are supported, open the information icon. Example: 2010-12-31 for 31 December 2010 in the New Era calendar.
- Date Range - this temporal coverage is meant to describe the time period within which the objects in the collection were collected. Selecting this temporal coverage type reveals a text box for a Start Date and a text box for an End Date, each with a calendar icon to the right with which a date can be selected.
  - Start Date - this text box is meant to contain the date the coverage began, in one of the supported date formats. To select a date, click on the calendar icon and choose a date, or enter the date manually. To find out what date formats are supported, open the information icon. Example: 2010-12-31 for 31 December 2010 in the New Era calendar.
  - End Date - this text box is meant to contain the date the coverage ended, in one of the supported date formats. To select a date, click on the calendar icon and choose a date, or enter the date manually. To find out what date formats are supported, open the information icon. Example: 2010-12-31 for 31 December 2010 in the New Era calendar.
- Formation Period - this temporal coverage type is meant to accommodate a named or other time period during which a collection or data set was assembled. Examples: "Victorian", "1922-1932", "c. 1750".
- Living Time Period - this temporal coverage type is meant to accommodate a named or other time period during which the biological entities in the collection or data set were alive, including palaeontological time periods. Examples: "1900-1950", "Ming Dynasty", "Pleistocene".

關鍵字

This metadata page allows the user to create one or more sets of keywords about the resource. Each set of keywords can be associated with a thesaurus/vocabulary that governs the terms in the list.

Remove this keyword set - click on this link to remove the keyword set that follows immediately below the link.
Thesaurus/Vocabulary - enter the name of a thesaurus or controlled vocabulary from which the keywords in the set are derived. If the keywords are not governed by a thesaurus/vocabulary, enter "n/a" indicating that it is not applicable in this text box. Example: IRIS keyword thesaurus.
Keyword List - enter a list of keywords, separated by commas that describe or are related to the resource.
Add new keyword set - click on this link to initiate a form for an additional keyword set.

計劃資料

This metadata page contains information about a project under which the data in the resource were produced.

Title - the title of the project.
Identifier - a unique identifier for the research project. This can be used to link multiple dataset/EML document instances that are associated in some way with the same project, e.g. a monitoring series. The nature of the association can be described in the project description.
Description - an abstract about the research project.
Funding - information about project funding and its sources (grant titles and numbers, contract numbers, names and addresses, active period, etc.). Other funding-related information may also be included.
Study Area Description - a description of the physical area where the project occurred (physical location, habitat, temporal coverage, etc.).
Design Description - a description of the design and objectives of the project. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.
Project Personnel - the list of people involved in the project.
- Personnel First Name - the first name of the person associated with the project.
- Personnel Last Name - the last name of the person associated with the project.
- Personnel Directory - the URL of the personnel directory system to which the personnel identifier belongs. There are four default directories to choose from: ORCID, ResearchID, LinkedIn, and Google Scholar. If you’d like to change the IPT’s default set of directories, refer to the Add a New User ID Directory page in the IPT wiki.
- Personnel Identifier - a 16-digit ORCID ID (e.g. 0000-0002-1825-0097) or another identifier that links this person to the personnel directory specified.
- Personnel Role - the role of the person associated with the project. Click on the information icon to the left of the select box to see descriptions of the possible roles. Choose the most appropriate role in the select box for the person named above.

取樣方法

This metadata page contains information about sampling methods used for the data represented by the resource.

IPTManageResourceMetadataSamplingMethods

Study Extent - a description of the physical and temporal conditions under which the sampling occurred. The geographic study extent is usually a surrogate (representative area of) for the larger area documented in the "Study Area Description" field of the Project metadata page.
Sampling Description - a text-based/human readable description of the sampling procedures used in the research project. The content of this element would be similar to a description of sampling procedures found in the methods section of a journal article.
Quality Control - a description of actions taken to either control or assess the quality of data resulting from the associated method step(s).
Step Description - A method step is one in a series of repeated sets of elements that document a series of methods and procedures used in the study, and the processing steps leading to the production of the data files. These include text descriptions of the procedures, relevant literature, software, instrumentation, source data and any quality control measures taken. Each method should be described in enough detail to allow other researchers to interpret and repeat, if required, the study.
Add new method step - click on this link to add a text box labelled "Step Description" to the page (see above). One may add as many method steps as desired.
Remove this method step - click on this link to remove the method step text box that follows immediately below the link.

引用文獻

This metadata page contains information about how to cite the resource as well as a bibliography of citations related to the data set, such as publications that were used in or resulted from the production of the data. Each Citation, whether for the resource or in the bibliography, consists of an optional unique Citation Identifier allowing the citation to be found among digital sources and a traditional textual citation. Before any Citation data are entered, the page will show a text box for the Citation Identifier for the resource, a text box for the Resource Citation, a heading labelled "Bibliographic Citations", and a link labelled "Add new bibliographic citation".

Free-text citations get overwritten on the GBIF.org dataset page - learn more in the GBIF FAQ.

Resource Citation - the single citation for use when citing the dataset.
- Example citation with institutional creator:
  
  Biodiversity Institute of Ontario (2011) Migratory birds of Ontario. Version 1.2. University of Guelph. Dataset/Species occurrences. https://doi.org/10.5886/qzxxd2pa
- Example citation with 9 creators:
  
  Brouillet L, Desmet P, Coursol F, Meades SJ, Favreau M, Anions M, Belisle P, Gendreau C, Shorthouse D (2010) Database of vascular plants of Canada. Version 1.2. Universite de Montreal Biodiversity Centre. Dataset/Species checklist. https://doi.org/10.5886/1bft7W5f
Auto-generation - Turn On/Off - turn on to let the IPT auto-generate the resource citation for you. The citation format used in auto-generation is based on DataCite’s preferred citation format, and satisfies the Joint Declaration of Data Citation Principles. This format includes a version number, which is especially important for datasets that are continuously updated. You can read more about the citation format in the Dataset Citation Format page in the IPT wiki.
Citation Identifier - a DOI, URI, or other persistent identifier that resolves to the online dataset. It is recommended the identifier be included in the citation. If the resource has been assigned a DOI (using the IPT), the IPT sets the DOI as the citation identifier and it can no longer be edited.
Bibliographic Citations - the additional citations of other resources related to or used in the creation of this resource.
Add new bibliographic citation - click on this link to add the text boxes required for an additional citation in the bibliography.
- Bibliographic Citation - the citation of an external resource related to or used in the creation of this resource.
- Bibliographic Citation Identifier - a DOI, URI, or other persistent identifier that resolves to the online external resource. It should be used in the citation, usually at the end.
- Remove this bibliographic citation - click on this link to remove the citation that follows immediately below the link.

採集、蒐藏資料

This metadata page contains information about the physical natural history collection associated with the resource (if any) as well as lists of types objects in the collection, called Curatorial Units, and summary information about them. Before any Collection data are entered, the page will show a header for each section (Collections, Specimen preservation methods, Curatorial Units) and a link labelled "Add new curatorial unit".

Collections - the list of collections that this resource is based on.
- Add new citation - click on this link to add the text boxes required for an additional collection in the Collections section.
- Collection Name - the full standard name by which the collection is known or cited in the local language.
- Collection Identifier - The URI (LSID or URL) of the collection. In RDF, used as URI of the collection resource.
- Parent Collection Identifier - Identifier for the parent collection for this sub-collection. Enables a hierarchy of collections and sub collections to be built. Please enter "Not applicable" if this collection does not have a parent collection.
- Remove this collection - click on this link to remove the collection that follows immediately below the link.
Specimen Preservation Methods - the list of specimen preservation methods covered by the resource, indicating the process or technique used to prevent physical deterioration of non-living collections. The values to choose from are based on the GBIF Specimen Preservation Method vocabulary. Remember you can include a list of preparations and preservation methods for a specimen in your data mapping DwC term preparations (http://rs.tdwg.org/dwc/terms/preparations). Please don’t select anything for treatments for living collections. This can relate to the curatorial unit(s) in the collection.
- Add new preservation method - click on this link to add the text boxes required for an additional preservation method in the Specimen Preservation Methods section.
- Remove this preservation method - click on this link to remove the preservation method that follows immediately below the link.
Curatorial Units - the counts of curatorial units covered by the resource. The count can be entered as a range or as a value with an uncertainty. Examples of units include skins, sheets, pins, boxes, and jars. Overall, this section summarizes the physical contents of the collection by type.
- Add new curatorial unit - click on this link to add the select text boxes required for an additional curatorial unit in the Curatorial Units section. When a new curatorial unit is added, the default Method Type selection is "Count Range".
- Method Type - this select box allows the user to choose from among two methods to specify the number of objects of a given type, either a count range, or a count with uncertainty. After making the selection, appropriate text boxes will appear allowing that counting method to the represented.
  - Count Range - this method type allows the user to set the lower and upper bounds on the number of objects of a particular unit type. See screen image above.
    
    Between - enter the lower bound of the number of objects in this text box.
    
    and - enter the upper bound of the number of objects in this text box.
  - Count with uncertainty - this method allows the user to set a number of objects of a particular unit type with an uncertainty above or below that number.
    
    Count - enter the mean likely number of object in this text box.
    
    +/- - enter the number of objects more or less than the number in the count text box for the range of possible counts of the particular unit type
  - Unit Type - the single type of object (specimen, lot, tray, box, jar, etc.) represented by the method type and count.
- Remove this curatorial unit - click on this link to remove the curatorial unit that follows immediately below the link.

外部連結

This metadata page contains links to the home page for the resource as well as links to the resource in alternate forms (database files, spreadsheets, linked data, etc.) and the information about them. Before any external links are entered, the page will show a text box for the Resource Homepage and a link labelled "Add new external link".

Resource Homepage - enter the full current URL of the web page containing information about the resource or its data set.
Other Data Formats - links to your resource data in other formats (e.g., database dumps, spreadsheets, nexus, linked data, etc.).
- Add new external link - click on the link having this text to add the text boxes required for an additional external link.
- Name - the name of the file or data set.
- Character Set - the name or code for the character encoding (e.g., ASCII, UTF-8).
- Download URL - the URL from which the file for the document or data set can be downloaded in the mentioned format.
- Data Format - the name or code of the document or file format (e.g., CSV, TXT, XLS, Microsoft Excel, MySQL).
- Data Format Version - the version of the document or file format given in the Data Format text box (e.g., 2003, 5.2).
- Remove this external link - click on the link having this label to remove the external link that follows immediately below.

其他元數據

This metadata page contains information about other aspects of the resource not captured on one of the other metadata pages, including alternative identifiers for the resource. Before any alternative identifiers are entered, the page will show text boxes for the purpose, maintenance description, additional metadata, a header for the Alternative Identifiers area, and a link labelled "Add new alternative identifier".

IPTManageResourceMetadataAdditionalMetadata

Date Created - the date on which the first version of the resource was published. It will be used to formulate the publication year in the auto-generated resource citation. This value is set automatically when publishing and cannot be edited.
Date Published - the date when the resource was last published. This value is set automatically when publishing (see the Publication section).
Resource logo URL - a logo representing the resource. The logo URL can be used to upload the resource. It may also be uploaded from an image file selected from your disk.
Purpose - a summary of the intentions for which the data set was developed. Includes objectives for creating the data set and what the data set is to support.
Maintenance Description - a description of the maintenance frequency of this resource. This description compliments the update frequency selected on the Basic Metadata page.
Additional Information - any information that is not characterized by the other resource metadata fields, e.g. history of the project, publications that have used the current data, information on related data published elsewhere, etc.
Alternative Identifiers - this section contains a list of additional or alternative identifiers for the resource. When the resource is published, the IPT’s URL to the resource is added to the list of identifiers. If a resource is assigned a new DOI using the IPT, the IPT ensures this DOI is placed first in the list of identifiers. When a resource is registered with the GBIF Registry, the Registry’s unique resource key is also added to the list of identifiers. If the resource represents an existing registered resource in the GBIF Registry, the existing registered resource UUID can be added to the list of identifiers. This will enable the IPT resource to update the existing resource during registration, instead of registering a brand new resource. For more information on how to migrate a resource, see this section.
- Add new alternative identifier - click on this link to add a text box for an alternative identifier for the resource.
- Alternative Identifier - the text for the alternative identifier for the resource (e.g., a URL, UUID, or any other unique key value).
- Remove this alternative identifier - click on this link to remove the alternative identifier that follows immediately below.

Publication

This area of the Resource Overview page allows a user to publish a version of the resource.

Click on the ┇ menu and select the "Publish" option to trigger publishing a new version. The "Publish" option will be enabled if

the required metadata for the resource are complete, and
the user has the role "Manager with/without registration rights".

Once the resource is registered only users with the role "Manager with registration rights" can publish, since the resource’s registration gets updated during each publication (see the explanation for Role in the "Create a new user" section under the "Configure User accounts" heading of the "Administration Menu" section). After pressing the "Publish" option, a confirmation dialog will appear:

The resource manager should enter a summary of what changes have been made to the resource (metadata or data) since the last/current version was published. The change summary is stored as part of the resource version history, and can be edited by resource managers via the resource homepage. A complete description of what happens after pressing "Publish" is explained in the "Publishing steps" section below.

Figure 1. A pending publication:

Shown here is table that compares the current version against the pending version. Resource managers can use this table to manage resource versioning, preview the pending version, plus review and validate the current version. The data in the table includes:

Version - the version number tracking the major_version.minor_version of the current/pending version. This is usually relevant only if you use the IPT-issued DOI workflow.
Current - current already published version.
Pending - next version.
License - resource license (e.g. CC0 1.0).
DOI - see DOI 工作流程 if IPT-issued DOIs is enabled.
Visibility - the visibility of the current/pending version. In order to register the resource with GBIF, the resource manager must ensure the current version is public.
Published on - to date the current version was published on / the date the pending version will be published on.
Publication log - button. Click to retrieve the "publication.log" of the current version. The resource manager can use the publication log to diagnose why publication failed for example. A more detailed description of its contents is described below in the Publishing Status page section. This is not applicable to the pending version.

Publishing steps

The publish action consists of the steps described below. Publication is all or nothing meaning that each step must terminate successfully in order for a new version to be published. If any step fails, or if the publish action is cancelled, the version is rolled back to the last published version.

The current metadata are written to the file eml.xml. An incremental version named eml-n.xml (where n is the incremental version number reflecting the publication version) is always saved.
A data publication document in Rich Text Format (RTF) is written to the file shortname.rtf. An incremental version of the RTF file named shortname-n.rtf is always saved.
The current primary resource data as configured through mapping are written to the Darwin Core Archive file named dwca.zip. The data files in the Darwin Core Archive are then validated (see "Data Validation" section below).
If the IPT’s Archival Mode is turned on (see Configure IPT settings section), an incremental version of the Darwin Core Archive file named dwca-n.zip is also saved.
The information about the resource is updated in the GBIF Registry if the resource is registered.
The DOI metadata about the resource is updated and propagated to DOI resolvers if the resource is assigned a DOI using the IPT.

Data Validation

The IPT writes data files inside the DwC-A as tab delimited files void of line breaking characters (note: line breaking characters found in the original data are replaced with an empty string).

After writing, the IPT also validates their content in the following ways:

If a column representing the core record identifier (e.g. occurrenceID is the core record identifier of the Occurrence core) is found in the core data file, the IPT will validate that for each record, the core record identifier is present, and unique.
The Darwin Core term basisOfRecord is a required term in the Occurrence extension. Therefore the IPT validates that each Occurrence data file has a basisOfRecord column. In addition, the IPT validates that for each Occurrence record the basisOfRecord is present, and its value matches the Darwin Core Type vocabulary.

Publishing Status page

A page entitled Publishing Status will show status messages highlighting the success or failure of each publishing step. Publication of a new version is an all or nothing event, meaning that all steps must finish successfully otherwise the version is rolled back.

Resource overview - This link leads to the Manage Resource page for the resource just published.
Publication log - This link initiates a download of a file named "publication.log", which contains the detailed output of the publication process. This file contains specific information to help managers identify problems during publication such as:
- how many records couldn’t be read and were not written to the DwC-A
- how many records were missing an identifier, or how many had duplicate identifiers (in the case that the core record identifier field was mapped)
- how many records contained fewer columns than the number that was mapped
Log message - The Publishing Status page shows a summary of the information that was sent to the filed named publication.log, which is stored in the directory for the resource within the IPT’s data directory and which is accessible through the link to the "Publication Log" immediately above the log message summary.

自動定期發布

To turn on automated publishing, in the Auto-publishing section click the ┇ menu and select "Edit".

Select one of the 5 publishing intervals (annually, biannually, monthly, weekly, or daily) and choose a time, then press "Save".

When automated publishing is on, the publishing interval and next published date are clearly displayed in the auto-publishing section. The "Edit" option can be used to change or disable auto-publishing.

In case of failure, publishing will be retried automatically up to 3 more times. This safeguards against infinite publishing loops. Resources configured to publish automatically, but that failed to finish successfully will have a next publication date in the past, and will be highlighted in the public and manage resource tables.

可見度

The Visibility area of the Manage Resources page allows users having manager rights for the resource to change its visibility state. The visibility of a resource determines who will be able to view it, and whether the resource can be registered with GBIF. By default, each resource is visible only to the user who created it and any other users who have the Admin role on the IPT where the resource is created. For explanations of each visibility state refer to the information below.

Private - A private resource is visible only to those who created it, or those who have been granted permission to manage it within the IPT, or by a user having the Admin role. This is primarily meant to preserve the resource from public visibility until it has been completely and properly configured.

When the resource is ready for public visibility, click on the ┇ menu and select the option labelled "Change". This will display a modal window with two options. You can make the resource public right away or at a set date

After submitting the form a message will appear at the top of the page saying that the status has been changed to "Public".
Public - A public resource is visible to anyone using the IPT instance where the resource is installed (on the table of public resource on the IPT Home page). The resource is ultimately accessible via the Internet to anyone who knows its homepage URL. However, the resource is not globally discoverable through the GBIF website until it has been registered with the GBIF Registry (see Registration).

One option appear in the ┇ menu of the visibility area. Clicking on the option labelled "Change" will display a modal window

Clicking on button labelled "Yes" will remove the resource entirely from public visibility and return it to the private state.
Registered - A resource that has been registered with the GBIF network is discoverable through the GBIF website and the data from the resource can be indexed by and accessed from the GBIF portal. Be aware it can take up to one hour for data to be indexed by GBIF following registration. A summary of information registered with GBIF will appear in the Registration area when registration is complete.

If the resource has already been registered, every time the "Publish" button is clicked, its registration information in the GBIF Registry also gets updated. The visibility of a registered resource can not be changed to private. If a resource must be removed from the GBIF Registry, follow the procedure described in the "Delete a Resource" section under the "Resource Overview" heading in the "Manage Resources Menu" section.

Registration

The resource is not globally discoverable through the GBIF website until it has been registered with the GBIF Registry.

Registration is enabled when:

the required metadata for the resource are complete,
the resource has been published (see the explanation of the Publication area of the Resource Overview page, below), and
the user has the role "Manager with registration rights" (see the explanation for Role in the "Create a new user" section under the "Configure User accounts" heading of the "Administration Menu" section). A user having the Admin role can grant the "Manager with registration rights" to any user.

Click on the ┇ menu and select the option labelled "Register" to register the resource with the GBIF Registry.

If you want this resource to update an existing registered DiGIR, BioCASe, or TAPIR resource, please refer to the section Migrate a Resource below

Clicking on this option will open a dialog box with which to confirm that you have read and understood the GBIF data sharing agreement, to which a link is given. Click on the check box to indicate that you agree with these terms. Doing so will cause a button labelled "Yes" to appear at the bottom of the dialog box. Click on "Yes" to register the resource, or click on "No" to defer the decision and close the dialog box.

IPTManageResourceVisibilityRegisterAgreement

If the attempt to register is successful, a message will appear at the top of the page saying that the status has been changed to "Registered". Registration section when the resource is registered:

網路

This section allows the resource to be included in one or more GBIF networks — collections of datasets potentially from many publishers, usually on a single theme. The largest network in GBIF is the Ocean Biodiversity Information System (OBIS).

To add the resource to a network, click on the ┇ menu and select the "Add" option. To remove it, click the ┇ menu on the network item and select "Delete".

Please only add your resource to a network with the approval of the network managers or the GBIF Help Desk.

資源管理者

Each resource has one or more explicitly assigned managers who are allowed to view, change, and remove the resource. The user who creates a resource automatically has these capabilities. Additional managers can be associated with a resource and given these same capabilities by selecting them by name from the select box in this area of the Resource Overview page, then clicking on the ┇ menu and selecting option labelled "Add". Any manager associated with a resource and having the role "Manager with registration rights" may also register the resource and update it in the GBIF registry. All users having the Admin role automatically have complete managerial roles for all resources in the IPT instance. The area shows the name and email address of the creator of the resource. If any managers have been added, their names and email addresses will be listed under the creator. Any added manager can have the managerial role for the resource removed by clicking on the respective ┇ menu and selecting the option labelled "Delete".

Delete a Resource

Clicking on the button labelled "Delete" on the Resource Overview page will display a modal confirmation window.

For registered with GBIF resources, it will display a modal window with two options.

Delete from the IPT and GBIF.org
Delete from the IPT only (Orphan)

Either options will remove the resource from the IPT and all of the related documents from the file system. The first will also delete the resource from GBIF.org.

Before deleting the resource, you can make a copy of the data in case you wish to restore it later. To do this, look on the server inside the IPT’s data directory, in the "resources" directory. Copy the directory (with the short name for the resource) to safe storage, somewhere outside the IPT’s data directory. A resource saved in this way can be re-integrated into the IPT, or integrated with a different IPT instance by following the procedure described in the "Integrate an existing resource configuration folder" section under the "Create a New Resource" heading in the "Manage Resources Menu" section.

Migrate a Resource

There is now a way to migrate existing registered DiGIR, BioCASe, TAPIR, or DwC-A resources to an IPT. This allows the existing resource to preserve its GBIF Registry UUID.

The way this works, is that the IPT resource is configured to update the existing registered resource that it corresponds to in the GBIF Registry.

To migrate an existing registered resource to your IPT resource, follow these instructions:

Ensure that the IPT resource’s visibility is public and NOT registered.
Determine the owning organization of the existing registered resource, ensure that it is added to the IPT as an organization, and that it is configured to publish datasets. To do so, please refer to the Add Organization section.
Select the owning organization from the drop-down list on the Basic Metadata page. Don’t forget to save the Basic Metadata page.
Go to the GBIF Dataset page of the existing registered resource. Depending on whether you are running the IPT in test or production mode, you would visit https://www.gbif-uat.org/dataset or https://www.gbif.org/dataset respectively.

Ensure the GBIF Dataset page shows the correct owning organization of the existing registered resource.

if it shows a different owning organization, the GBIF Registry must be updated before you can proceed with the remaining steps. Send an email to helpdesk@gbif.org alerting them to the update needed.

Copy the GBIF Registry UUID from the GBIF Dataset page URL, e.g 5d637678-cb64-4863-a12b-78b4e1a56628.
Add this UUID to the list of the IPT resource’s alternative identifiers on the Additional Metadata page. Don’t forget to save the Additional Metadata page.
Ensure that no other public or registered resource in your IPT includes this UUID in their list of alternative identifiers. In cases where you are trying to replace a registered resource that already exists in your IPT, the other resource has to be deleted first.
On the resource overview page, click the register button. Similar to any other registration, you will have to confirm that you have read and understood the GBIF data sharing agreement before the registration will be executed.

You will receive a confirmation message like this, showing the existing dataset in GBIF has been updated.
If applicable, email helpdesk@gbif.org alerting them whether the DiGIR/BioCASe/TAPIR/IPT technical installation that used to serve the resource has been deprecated, and whether it can be deleted from the GBIF Registry