koha-manual/webservices — Chinese (Traditional) @ Weblate: OpacBaseURL/cgi-bin/koha/svc/report?id=REPORTID

Translation

English

Chinese (Traditional)

Needs editing

Skip

	English	Chinese (Traditional)	Actions
	If operation=searchRetrieve, then the search key should be query. As in : operation=searchRetrieve&query=reefs	若 operation=searchRetrieve，則搜尋鍵詞應為詢問。如：operation=searchRetrieve&query=reefs
	If operation=scan, then the search key should be scanClause. As in : operation=scan&scanClause=reefs	若 operation=scan，則搜尋鍵詞應為 scanClause。如：operation=scan&scanClause=reefs
	etc/zebradb/biblios/etc/bib1.att defines Zebra/3950 indexes that exist on your system. For instance you'll see that we have indexes for Subject and for Title: att 21 Subject and att 4 Title respectively.	etc/zebradb/biblios/etc/bib1.att 定義系統內存在的 Zebra/3950 索引。如：可看到對主題與題名的索引分別是：att 21 Subject 與 att 4 Title。
	In the pqf.properties file located under etc/zebradb/pqf.properties I see that an access point already uses my Subject index (index.dc.subject = 1=21) while another uses my Title index (index.dc.title = 1=4) I know this is my Subject index because as I've seen just before in my bib1.att file, it's called with =1=21 in Z3950: so index.dc.subject = 1=21 correctly points to my Subject index. And Title was called with 1=4 so index.dc.title = 1=4 correctly points to my Title index. I can now construct my query just like I would in a search box, just preceding it with the "query" key: query=Subject=reefs and Title=coral searches "reefs" in the subject and "coral" in the title. The full url would be http://myserver.com:9999/biblios?version=1.1&operation=searchRetrieve&query=Subject=reefs and Title=coral If I want to limit the result set to just 5 records, I can do http://myserver.com:9999/biblios?version=1.1&operation=searchRetrieve&query=Subject=reefs and Title=coral&maximumRecords=5	當另個使用者使用我的題名索引 (index.dc.title = 1=4) 就可看到位在 etc/zebradb/pqf.properties 的 pqf.properties 檔案已使用我的主題索引 (index.dc.subject = 1=21) 我知道這個是我的主題索引因為在我的 bib1.att 檔案裡見過它，稱為 with =1=21 於 Z3950: 所以 index.dc.subject = 1=21 精確指向我的主題索引。且題名為 1=4 所以 index.dc.title = 1=4 精確指向題名索引。我可以像在搜尋盒裡一樣建構自己的搜尋，祗要加入 "query" 鍵：query=Subject=reefs and Title=coral 在主題內搜尋 "reefs" 且在題名內搜尋 "coral"。完整的網址像是這樣 http://myserver.com:9999/biblios?version=1.1&operation=searchRetrieve&query=Subject=reefs and Title=coral 若我要限制祗呈現 5 筆記錄，則為 http://myserver.com:9999/biblios?version=1.1&operation=searchRetrieve&query=Subject=reefs and Title=coral&maximumRecords=5
	I can also play with truncate, relations, etc. Those are also defined in my pqf.properties file. I can see for instance the position properties defined as:	我也可使用截切、相關等用法。它們都定義在我的 pqf.properties 檔案內。我可看到其用法如：
	So as an example if I want "coral" to be at the beginning of the title, I can do this query : http://myserver.com:9999/biblios?version=1.1&operation=searchRetrieve&query=Title=coral first	所以，舉例來說我想要找尋題名起頭為 "coral" 的紀錄，我可以做這樣的搜尋：http://myserver.com:9999/biblios?version=1.1&operation=searchRetrieve&query=Title=coral first
	Retrieve	取得搜尋結果
	My search for http://univ\_lyon3.biblibre.com:9999/biblios?version=1.1&operation=searchRetrieve&query=coral reefs&maximumRecords=1 retrieves just on record. The response looks like this:	我的搜尋 http://univ\_lyon3.biblibre.com:9999/biblios?version=1.1&operation=searchRetrieve&query=coral reefs&maximumRecords=1 提取一筆紀錄。回應的內容像這樣：
	ILS-DI	ILS-DI
	As of writing, the self documenting ILS-DI is the most complete interface. After it has been enabled as described in the :ref:`ILS-DI system preferences <webservices-ils-di-system-preferences-label>` section, the documentation should be available at https://YOURKOHACATALOG/cgi-bin/koha/ilsdi.pl	撰寫之後，自我生成的 ILS-DI 就是完整的介面，經由 :ref:`ils-di-label`系統偏好的設定後，該文件可以從 https://YOURKOHACATALOG/cgi-bin/koha/ilsdi.pl 取得
	JSON reports services	JSON 報表服務
	Koha implements a JSON reports service for every report saved using the :ref:`Guided reports wizard <guided-report-wizard-label>` or :ref:`Report from SQL <report-from-sql-label>` features.	Koha 把 JSON 報表服務應用在儲存於 :ref:`報表精靈 <guided-report-wizard-label>` 或 :ref:`來自 SQL 的報表 <report-from-sql-label>` 功能中。
	By default reports will be non-public and only accessible by authenticated users. If a report is explicitly set to public it will be accessible without authentication by anyone. This feature should only be used when the data can be shared safely not containing any patron information.	報表預設為不公開祗有被授權的使用者才能看到。若揭示為公開則任何人均可看到。祗有不含個人資訊的報表，才可以公開。
	The reports can be accessed using the following URLs:	經由以下的 URL 近用該等報表：
	Public reports	公開的報表
	OpacBaseURL/cgi-bin/koha/svc/report?id=REPORTID	OpacBaseURL/cgi-bin/koha/svc/report?id=REPORTID
	Non-public reports	不公開的報表
	StaffBaseURL/cgi-bin/koha/svc/report?id=REPORTID	StaffBaseURL/cgi-bin/koha/svc/report?id=REPORTID
	There are also some additional parameters available:	還有其他可用的參數：
	Instead of accessing the report by REPORTID you can also use the report's name:	以 REPORTID 近用報表之外，還可以用報表名稱近用它們：
	.../cgi-bin/koha/svc/report?name=REPORTNAME	.../cgi-bin/koha/svc/report?name=REPORTNAME
	For easier development there is also an option to generate an annotated output of the data. It will generate an array of hashes that include the field names as keys.	還有簡易的方法產生資料。產生以欄位名稱為鍵詞的陣列。
	.../cgi-bin/koha/svc/report?name=REPORTNAME&annotated=1	.../cgi-bin/koha/svc/report?name=REPORTNAME&annotated=1
	Versioned RESTful API effort	可視的 RESTful API Effort
	There is an ongoing effort to converge the APIs above into a single versioned set of modern RESTful endpoints documented using the OpenAPI standard and available by default under https://YOURKOHACATALOG/api/v1/	以 OpenAPI 標準轉換前述的 API 至現代的 RESTful 文件，預設的位置為 https://YOURKOHACATALOG/api/v1/
	OAuth2 client credentials grant	授與 OAuth2 客戶端認證
	Koha supports the OAuth2 client credentials grant as a means to secure the API for using it from other systems to adhere to current industry standards. More information on the OAuth2 client credentials grant standard `can be found here <https://auth0.com/docs/api-auth/grant/client-credentials>`_.	Koha 支援授與 OAuth2 客戶端認證做為 API 安全機制。詳情見 `可在此找到 <https://auth0.com/docs/api-auth/grant/client-credentials>`_。
	API key management interface for patrons	讀者的 API 金鑰管理介面
	In order for API keys to be create for patrons, the system preference :ref:`RESTOAuth2ClientCredentials <restoauth2clientcredentials-label>` must be enabled for the option to appear in a patron record.	為了讓讀者新增 API 金鑰，系統偏好 :ref:`RESTOAuth2ClientCredentials` 必須啟用才能在讀者紀錄內顯示該選項。
	Navigate to a patron record and select More > Manage API keys	瀏覽讀者紀錄並選擇更多 > 管理 API 金鑰
	\|image1336\|

Loading…

None

String updated in the repository

English

Chinese (Traditional) 47 characters edited Current translation Translated

a year ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Chinese (Traditional)
Koha		Base terminology
Use "Koha", not "KOHA" or "koha" when referring to the Koha integrated library software and the Koha project. Koha is not an abbreviation, initialism, or acronym.
KOHA		Base terminology
Do not use. Use "Koha" when referring to the Koha integrated library software and the Koha project.

String information

Source string location

../../source/webservices.rst:339

String age

a year ago

Last updated

4 months ago

Source string age

a year ago

Translation file

zh_Hant/LC_MESSAGES/webservices.po, string 45