X-Git-Url: http://git.indexdata.com/?p=idzebra-moved-to-github.git;a=blobdiff_plain;f=doc%2Fquickstart.xml;h=b7daa8c2cc1972074cb02e661e76c5a6b0bb9486;hp=3fe2d2c6bc9510532b096fe4effcf1a149b6df70;hb=972bceaa6386f904bc3e4845f1c5598656c5c6f2;hpb=bb39ca3dd76e6339f66813bca1e64b644760e5a2 diff --git a/doc/quickstart.xml b/doc/quickstart.xml index 3fe2d2c..b7daa8c 100644 --- a/doc/quickstart.xml +++ b/doc/quickstart.xml @@ -1,104 +1,104 @@ - - Quick Start + + Quick Start - - - In this section, we will test the system by indexing a small set of - sample GILS records that are included with the &zebra; distribution, - running a &zebra; server against the newly created database, and - searching the indexes with a client that connects to that server. - - - Go to the examples/gils subdirectory of the - distribution archive. The 48 test records are located in the sub - directory records. To index these, type: - - zebraidx update records - - - - - In this command, the word update is followed - by the name of a directory: zebraidx updates all - files in the hierarchy rooted at that directory. - - - - If your indexing command was successful, you are now ready to - fire up a server. To start a server on port 2100, type: - - - zebrasrv @:2100 - - - + + + In this section, we will test the system by indexing a small set of + sample GILS records that are included with the &zebra; distribution, + running a &zebra; server against the newly created database, and + searching the indexes with a client that connects to that server. + + + Go to the examples/gils subdirectory of the + distribution archive. The 48 test records are located in the sub + directory records. To index these, type: + + zebraidx update records + + + + + In this command, the word update is followed + by the name of a directory: zebraidx updates all + files in the hierarchy rooted at that directory. + + + + If your indexing command was successful, you are now ready to + fire up a server. To start a server on port 2100, type: + + + zebrasrv @:2100 + - - The &zebra; index that you have just created has a single database - named Default. - The database contains records structured according to - the GILS profile, and the server will - return records in &acro.usmarc;, &acro.grs1;, or &acro.sutrs; format depending - on what the client asks for. - - - - To test the server, you can use any &acro.z3950; client. - For instance, you can use the demo command-line client that comes - with &yaz;: - - - - yaz-client localhost:2100 - - - - - When the client has connected, you can type: - - - - - Z> find surficial - Z> show 1 - - - - - The default retrieval syntax for the client is &acro.usmarc;, and the - default element set is F (``full record''). To - try other formats and element sets for the same record, try: - - - - Z>format sutrs - Z>show 1 - Z>format grs-1 - Z>show 1 - Z>format xml - Z>show 1 - Z>elements B - Z>show 1 - - - - - You may notice that more fields are returned when your - client requests &acro.sutrs;, &acro.grs1; or &acro.xml; records. - This is normal - not all of the GILS data elements have mappings in - the &acro.usmarc; record format. - - - If you've made it this far, you know that your installation is - working, but there's a certain amount of voodoo going on - for - example, the mysterious incantations in the - zebra.cfg file. In order to help us understand - these fully, the next chapter will work through a series of - increasingly complex example configurations. - - - + + + The &zebra; index that you have just created has a single database + named Default. + The database contains records structured according to + the GILS profile, and the server will + return records in &acro.usmarc;, &acro.grs1;, or &acro.sutrs; format depending + on what the client asks for. + + + + To test the server, you can use any &acro.z3950; client. + For instance, you can use the demo command-line client that comes + with &yaz;: + + + + yaz-client localhost:2100 + + + + + When the client has connected, you can type: + + + + + Z> find surficial + Z> show 1 + + + + + The default retrieval syntax for the client is &acro.usmarc;, and the + default element set is F (``full record''). To + try other formats and element sets for the same record, try: + + + + Z>format sutrs + Z>show 1 + Z>format grs-1 + Z>show 1 + Z>format xml + Z>show 1 + Z>elements B + Z>show 1 + + + + + You may notice that more fields are returned when your + client requests &acro.sutrs;, &acro.grs1; or &acro.xml; records. + This is normal - not all of the GILS data elements have mappings in + the &acro.usmarc; record format. + + + + If you've made it this far, you know that your installation is + working, but there's a certain amount of voodoo going on - for + example, the mysterious incantations in the + zebra.cfg file. In order to help us understand + these fully, the next chapter will work through a series of + increasingly complex example configurations. + + +