My endnote says server excution failed2/16/2023 “reefs” in the subject and “coral” in the title. With the “query” key: query=Subject=reefs and Title=coral searches I can nowĬonstruct my query just like I would in a search box, just preceding it Index.dc.title = 1=4 correctly points to my Title index. This is my Subject index because as I’ve seen just before in my bib1.attįile, it’s called with =1=21 in Z3950: so index.dc.subject = 1=21Ĭorrectly points to my Subject index. = 1=21) while another uses my Title index (index.dc.title = 1=4) I know See that an access point already uses my Subject index (index.dc.subject In the pqf.properties file located under etc/zebradb/pqf.properties I For instance you’ll see that we have indexes for SubjectĪnd for Title: att 21 Subject and att 4 Title respectively. As in :Įtc/zebradb/biblios/etc/bib1.att defines Zebra/3950 indexes that exist If operation=scan, then the search key should be scanClause. If operation=searchRetrieve, then the search key should be query. The “operation” key can take two values: scan or searchRetrieve. Koha 3 Bibliographic SRU/SRW/Z39.50 server To enable OAI-PMH in Koha edit the OAI-PMH preference. The biggest stumbling block to having Koha harvestįrom other repositories is that MARC is the only metadata format that Koha at present can only act as a Data Provider. The Data Providers rather, services are based on the harvested data via Note that this means that there are no live search requests to Use the OAI interfaces of the Data Providers to harvest and store Implement, low barrier solution for Data Providers. Data Providers (open archives, repositories) provideįree access to metadata, and may, but do not necessarily, offer freeĪccess to full texts or other resources. (OAI-PMH) there are two groups of ‘participants’: Data Providers and For the Open Archives Initiative-Protocol for Metadata Harvesting
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |