koha-manual/webservices — Czech @ Weblate: Explain

Zen

	English	Czech	Actions
	OAI-PMH	OAI-PMH
	For the Open Archives Initiative-Protocol for Metadata Harvesting (OAI-PMH) there are two groups of 'participants': Data Providers and Service Providers. Data Providers (open archives, repositories) provide free access to metadata, and may, but do not necessarily, offer free access to full texts or other resources. OAI-PMH provides an easy to implement, low barrier solution for Data Providers. Service Providers use the OAI interfaces of the Data Providers to harvest and store metadata. Note that this means that there are no live search requests to the Data Providers; rather, services are based on the harvested data via OAI-PMH.	Z hlediska protokolu Open Archives Initiative-Protocol for Metadata Harvesting (OAI-PMH) existují dvě skupiny účastníků při předávání metadat: Data Providers (poskytovatelé dat) a Service Providers (poskytovatelé služeb). Poskytovatelé dat (archívy, repozitáře) poskytují volný přístup k metadatům a mohou (ale nemusejí) poskytovat i volný přístup k plným textům a dalším zdrojům. OAI-PMH je z hlediska poskytovatelů dat poměrně snadno implementovatelný. Poskytovatelé služeb sklázejí data od data providerů a ukládají je do svých databází. To znamená, že poskytovatelé služeb nezprostředkovávají přímý přístup k aktuálním datům u poskytovatelů dat, ale poskytované služby jsou založené na těch datech, která jsou sklizena a uložena přes OAI-PMH.
	Learn more about OAI-PMH at: http://www.openarchives.org/pmh/	Více o protokolu OAI-PMH se dozvíte na: http://www.openarchives.org/pmh/
	Koha at present can only act as a Data Provider. It can not harvest from other repositories. The biggest stumbling block to having Koha harvest from other repositories is that MARC is the only metadata format that Koha indexes natively.	Koha v současné době umí být pouze poskytovatelem dat. Neumí tedy sbírat data z jiných repozitářů. Největší překážkou je to, že Koha ukládá všechny záznamy pouze ve formátu MARC. Chcete-li vědět více o tom, jak OAI-PMH funguje, navštivte tuto stránku: http://www.oaforum.org/tutorial/english/page3.htm
	To enable OAI-PMH in Koha edit the :ref:`OAI-PMH <oai-pmh-pref-label>` preference. Once enabled you can visit http://YOURKOHACATALOG/cgi-bin/koha/oai.pl to see your file.
	By default Koha won't include item information in OAI-PMH result sets, but they can be added by using the include_items option in the a configuration file linked from :ref:`OAI-PMH:ConfFile <oai-pmh-conffile-label>`.	Koha ve výchozím nastavení OAI-PMH neposkytuje informace o jednotkách. Lze je však doplnit použitím parametru include_items v konfiguračním souboru odkazovaným z :ref:`OAI-PMH:ConfFile`.
	Note that the sample conf file below contains both marc21 and marcxml, because marc21 is the metadata prefix recommended by the `OAI-PMH guidelines <https://www.openarchives.org/OAI/2.0/guidelines-marcxml.htm>`_ while marcxml was the only one in the sample before Koha 23.11 (and support for marc21 was added in Koha 17.05).
	Sample OAI conf file	Příklad konfigurační souboru po OAI
	The options are:
	xsl\_file: Path to an XSLT file that will be used for transforming the Koha MARCXML data into the needed structure/format. It can be useful, for example, if you need some specific Dublin Core fields to be generated instead of just the default ones.
	include\_items: If set to 1, item information will be included in the response according to the MARC framework's mapping.
	expanded\_avs: If set to 1, all coded values will the expanded with descriptions. This includes library names, item type descriptions, authorized value descriptions and classification source descriptions.
	All these options can be used with different metadataPrefix entries, allowing the consumers to request one or the other.
	SRU server	SRU server
	Koha implements the Search/Retrieve via URL (SRU) protocol. More information about the protocol itself can be found at http://www.loc.gov/standards/sru/. The version implemented is version 1.1.
	Explain	Explain
	If you want to have information about the implementation of SRU on a given server, you should have access to the Explain file using a request to the server without any parameter. Like http://myserver.com:9999/biblios/. The response from the server is an XML file that should look like the following and will give you information about the default settings of the SRU server.
	Search	Hledat
	This url : http://myserver.com:9999/biblios?version=1.1&operation=searchRetrieve&query=reefs is composed of the following elements:
	base url of the SRU server : http://myserver.com:9999/biblios?
	search part with the 3 required parameters : version, operation and query. The parameters within the search part should be of the key=value form, and can be combined with the & character.
	One can add optional parameters to the query, for instance maximumRecords indicating the maximum number of records to be returned by the server. So http://myserver.com:9999/biblios?version=1.1&operation=searchRetrieve&query=reefs&maximumRecords=5 will only get the first 5 results results from the server.
	The "operation" key can take two values: scan or searchRetrieve.
	If operation=searchRetrieve, then the search key should be query. As in : operation=searchRetrieve&query=reefs
	If operation=scan, then the search key should be scanClause. As in : 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.
	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
	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:
	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
	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: