X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fadministration.xml;h=d47fc776959c255b541814ebe8f64cddac52de99;hb=b19b79e382ef8196f1625763db1af3a82b1e0c81;hp=13baec6a252641c36832553f132ed9be26a2e0de;hpb=5ca4e60e990af6ad6b62ebff855d7b642f37c3ec;p=idzebra-moved-to-github.git diff --git a/doc/administration.xml b/doc/administration.xml index 13baec6..d47fc77 100644 --- a/doc/administration.xml +++ b/doc/administration.xml @@ -1,5 +1,5 @@ - + Administrating &zebra; @@ -418,7 +418,7 @@ of permissions currently: read (r) and write(w). By default users not listed in a permission directive are given the read privilege. To specify permissions for a user with no - username, or Z39.50 anonymous style use + username, or &z3950; anonymous style use anonymous. The permstring consists of a sequence of characters. Include character w for write/update access, r for read access and @@ -465,7 +465,7 @@ mounted on a CD-ROM drive, you may want &zebra; to make an internal copy of them. To do this, you specify 1 (true) in the storeData setting. When - the Z39.50 server retrieves the records they will be read from the + the &z3950; server retrieves the records they will be read from the internal file structures of the system. @@ -494,7 +494,7 @@ Consider a system in which you have a group of text files called simple. - That group of records should belong to a Z39.50 database called + That group of records should belong to a &z3950; database called textbase. The following zebra.cfg file will suffice: @@ -613,7 +613,7 @@ information. If you have a group of records that explicitly associates an ID with each record, this method is convenient. For example, the record format may contain a title or a ID-number - unique within the group. - In either case you specify the Z39.50 attribute set and use-attribute + In either case you specify the &z3950; attribute set and use-attribute location in which this information is stored, and the system looks at that field to determine the identity of the record. @@ -700,7 +700,7 @@ For instance, the sample GILS records that come with the &zebra; distribution contain a unique ID in the data tagged Control-Identifier. - The data is mapped to the Bib-1 use attribute Identifier-standard + The data is mapped to the &bib1; use attribute Identifier-standard (code 1007). To use this field as a record id, specify (bib1,Identifier-standard) as the value of the recordId in the configuration file. @@ -1049,7 +1049,7 @@ The experimental alvis filter provides a - directive to fetch static rank information out of the indexed XML + directive to fetch static rank information out of the indexed &xml; records, thus making all hit sets ordered after ascending static rank, and for those doc's which have the same static rank, ordered @@ -1086,21 +1086,21 @@ indexing time (this is why we call it ``dynamic ranking'' in the first place ...) It is invoked by adding - the Bib-1 relation attribute with - value ``relevance'' to the PQF query (that is, + the &bib1; relation attribute with + value ``relevance'' to the &pqf; query (that is, @attr 2=102, see also - The BIB-1 Attribute Set Semantics, also in + The &bib1; Attribute Set Semantics, also in HTML). To find all articles with the word Eoraptor in - the title, and present them relevance ranked, issue the PQF query: + the title, and present them relevance ranked, issue the &pqf; query: @attr 2=102 @attr 1=4 Eoraptor - Dynamically ranking using PQF queries with the 'rank-1' + <title>Dynamically ranking using &pqf; queries with the 'rank-1' algorithm @@ -1167,7 +1167,7 @@ It is possible to apply dynamic ranking on only parts of the - PQF query: + &pqf; query: @and @attr 2=102 @attr 1=1010 Utah @attr 1=1018 Springer @@ -1202,7 +1202,7 @@ Ranking weights may be used to pass a value to a ranking - algorithm, using the non-standard BIB-1 attribute type 9. + algorithm, using the non-standard &bib1; attribute type 9. This allows one branch of a query to use one value while another branch uses a different one. For example, we can search for utah in the @@ -1214,7 +1214,7 @@ The default weight is - sqrt(1000) ~ 34 , as the Z39.50 standard prescribes that the top score + sqrt(1000) ~ 34 , as the &z3950; standard prescribes that the top score is 1000 and the bottom score is 0, encoded in integers. @@ -1339,7 +1339,7 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci @@ -1555,10 +1555,10 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci - Extended services in the Z39.50 protocol + Extended services in the &z3950; protocol - The Z39.50 standard allows + The &z3950; standard allows servers to accept special binary extended services protocol packages, which may be used to insert, update and delete records into servers. These carry control and update @@ -1566,7 +1566,7 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci - Extended services Z39.50 Package Fields + Extended services &z3950; Package Fields @@ -1594,13 +1594,13 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci record - XML string - An XML formatted string containing the record + &xml; string + An &xml; formatted string containing the record syntax 'xml' - Only XML record syntax is supported + Only &xml; record syntax is supported recordIdOpaque @@ -1663,7 +1663,7 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci When retrieving existing - records indexed with GRS indexing filters, the &zebra; internal + records indexed with &grs1; indexing filters, the &zebra; internal ID number is returned in the field /*/id:idzebra/localnumber in the namespace xmlns:id="http://www.indexdata.dk/zebra/", @@ -1712,7 +1712,7 @@ where g = rset_count(terms[i]->rset) is the count of all documents in this speci ]]> Now the Default database was created, - we can insert an XML file (esdd0006.grs + we can insert an &xml; file (esdd0006.grs from example/gils/records) and index it: rset) is the count of all documents in this speci Extended services from yaz-php - Extended services are also available from the YAZ PHP client layer. An - example of an YAZ-PHP extended service transaction is given here: + Extended services are also available from the &yaz; &php; client layer. An + example of an &yaz;-&php; extended service transaction is given here: A fine specimen of a record';