Programs

The scientific and technical library of tpu conducts internships for work in abis “ruslan. Automated library and information system "ruslan"

Scientific and technical library Tomsk Polytechnic University
internships for work in the automated library and information system "Ruslan"
for specialists from other libraries. Internships are organized by contracts.
The number of hours and the program are formed individually at the request of the libraries.

Contact Information
Tomsk, st. Belinsky 55,
Scientific and technical library of Tomsk Polytechnic University.
Simakovskaya Svetlana Gennadievna innovation-methodical department of NTB TPU, tel. (8-3822) 55-80-42, e-mail: [email protected]
Chuprikova Natalya Trofimovna, chief librarian-technologist,
tel. (8-3822) 56-37-48, e-mail: [email protected]

Sample program:

Topic 1. General acquaintance with the work of the library
Tour of the library. Mission, policy, structure of NTB. Organizational and regulatory documentation, QMS documentation, Comprehensive Program for the Development of NTBs. Participation of the library in projects.

Topic 2. Organizational and technological aspects of library automation
Implementation of ABIS in NTB TPU. Library program. Tasks and principles of technological work. The necessary conditions and stages of ABIS implementation. Development of a local area network (LAN). Development of technological documentation. Technological management and control. Training.

Topic 3. Automated library and information system (ABIS) "Ruslan"
Compound, a brief description of and purpose of the system. General principles ABIS organizations. Main components: Ruslan Server, DBMS, Administrator's workstation, Acquisition/Cataloging workstation, Book issue workstation, OPAS, Reader's workstation, MBA workstation.

The main functions of the Ruslan server. Basic operations of searching, extracting, inserting, deleting, changing and others. Support for bibliographic and authoritative databases (MARC), specialized databases (Explain, Extended), service databases (reference books, readers, acts, KSU). Access control to the database by user categories. Multilingual data support (UNICODE).

The main functions of the Administrator's Workstation. Management of the server and access rights to the database. Establishment and support of the database. Record indexing and batch editing. Restoring a deleted or modified record in a bibliographic database. Backup DB. Rollback to previous versions records. Notification of ABIS users. Loading/unloading records from a file. Statistics of work, history of work of any user with ABIS. Security management.

Topic 4. RUSMARC
Submission and updating of formats on the website of the National Service for the Development of the RUSMARC Format System at http://www.rba.ru:8101/rusmarc/

Russian communicative format for the presentation of bibliographic records. Basic concepts. Standards and rules. Purpose and structure of the format. The composition of the record. Marker. blocks of information. Composition of fields, subfields. Communication fields. Guidelines for the description of certain types of documents in the RUSMARC format.

Russian communicative format for presenting authoritative/normative records. Definitions. Principles of construction and purpose of the format. Format records: authoritative/normative, reference and reference. Function blocks. Link tracing.
Topic 5
Ordering documents on electronic price lists and thematic plans publishing houses. Order formation in ABIS "Ruslan". Forming a copy of the order and sending it to the publisher by e-mail or fax.

Borrowing records from the database of the Russian Communist Party and the National Library of Russia. Inventory number generator. Create records from templates. Double check. Conducting invoices and write-offs. Output forms in MS Excel format: Automated Book of total accounting (KSU); Inventory book. Formation of accounting documents for accounting (acts, reports, etc.). Distribution of documents by storage symbols. Transfer of travel documents.

Topic 6. Formation of an electronic catalog of periodicals
Subscription of periodicals and information publications in ABIS "Ruslan". Output forms in MS Excel format: Copy of application for subscription, delivery cards. Accounting and registration of new receipts of periodicals. Maintenance of the electronic catalog "Periodicals". Multilevel cataloging of periodicals.

Topic 7. Book availability of the educational process
The Book Provision Program. Formation of directories. Entering information about the educational process of the university. Work with lists of recommended literature for disciplines. Import of information from ORAS ABIS "Ruslan". Generation of book supply reports.

Topic 8
Systematization. Classification schemes in NTB: Universal Decimal Classification (UDC), Library and Bibliographic Classification (LBC), All-Russian Classification of Specialties of Highest Scientific Qualification (oksvnk). Subjectization (definition of keywords). Reference book of keywords.

Bibliographic description of documents in the electronic catalog with full support RUSMARC format (link fields, link tracing, authority files). Setting the record format (fields, subfields, lists, value sets, directories, etc.). Input various types records according to corporate templates and instructions. Contextual help on the RUSMARC record format. Maintain directories and authority files. UNICODE support using builtin virtual keyboard. Closing of accounts and transfer of documents to fund holders.

Technology of retro-entry of documents. Borrowing records from external sources.

Topic 9. Creating a Bulletin of New Arrivals
Purpose and structure of the bulletin. Formation technology in the Acquisition / Cataloging AWP. The process of editing bibliographic descriptions. Preparing a bulletin for placement on the WWW-server in the New Arrivals section.

Topic 10. Analytical painting
Analytical description of articles from periodicals. Description template "Periodicals-Analytics". Communication fields. Definition of keywords.

Analytical description of articles from books, works and materials of conferences. Description template "Analytics from the book". Communication fields. Definition of keywords.

Topic 11. Formation of the TPU Digital Library
Tasks and functions. technologies for collecting, storing, technical processing electronic versions of publications of TPU employees, digitization of hard copies, their presentation in the electronic catalog of the NTB. Methodology for describing an electronic resource. Description templates for an electronic resource: dissertation abstract, dissertation, floppy disk, CD-ROM, remote resource.

Topic 12. The main functions of the Reader's workstation
Search modes: Search, Search and order, Order execution control. User identification. User guide. Methodology for compiling search queries. Simple and advanced search. Information about the location and availability of free copies of documents.

Technology of consulting work on the electronic catalog.
Methodology for teaching users to work in the electronic catalog.

Topic 13
Registration / re-registration of users. Electronic form of the user. Laminated library card. Statistics on a single reader's ticket.

Receipt / issue and accounting of issued documents using bar-coding technology for library cards and documents. Doing electronic queues on you this document. Working with debtors Information about issued documents, current orders, users by various search criteria.
Technology of work on the subscription and in the reading room. Addition of barcodes of documents from the AWP of Book Loan. Technology of execution and completion of orders in book storage and on the loan. Work statistics.

Topic 14. Main functions of AWP MBA
Search for bibliographic information in the electronic catalog. Ordering IBA services: a document for temporary use, a copy of the document, a certificate of location, a certificate of the cost of delivery of the document. Order cancellation. Notifications: about sending a document to the subscriber, about the timing of the order, and others. Denial of service with a reason. Incoming and outgoing orders.

Use of Z39.50 and ISO ILL protocols.

Topic 15. Round table (for specialists from other libraries)
Summing up the internship. Answers on questions. Setting tasks for the implementation of ABIS. Recommendations for further work.

Ministry of Education of the Russian Federation

Barnaul State Pedagogical University

________________________________________________________________

I approve

Rector of BSPU

________________

"____" _______________ 2004

Technological instruction for creating an analytical description of an article from the collection in the ABIS "Ruslan" in the reference and bibliographic department of the NPB BSPU

Vice-Rector for Innovation and Information Technology

__________

"____" __________ 2004

NB Director

________

"____" ____________ 2004

2004

The aim of the work is to create machine-readable bibliographic records in the RUSMARC format for documents of an analytical level. The work is carried out by means of the AWP of the kit-catalogizer in the Ruslan program.

The description of documents is created in the Acquisition Department, finalized in the Cataloging Department, therefore, when creating a record for an article, a number of fields are already filled in, for some fields the values are set by default or automatically.

The task of the bibliographer is to supplement the given document with the necessary elements of description by filling in the missing fields.

When filling in fields and subfields, remember:

Punctuation marks are not used at the end of fields and subfields;

Analytical document processing:

Articles are systematized according to LBC tables (Library and Bibliographic Classification).

Are determined keywords according to " methodological recommendations on coordinate indexing.

Creating a new bibliographic record:

Select the name of the desired recording template from the menu of the main window "Record - Create a new bibliographic" - "Analytics from the book" or use the button "B".

The fields (subfields) of the template are preconfigured.

Check if the parameters are filled in correctly Marker.

The record marker (pointer) is located at the beginning of each record of the Russian communicative format. Contains the data needed to process the record.

6 Record type (a) - text materials, printed - is set by default.

7 Bibliographic level (а) – analytical.

8 Hierarchical level code (2) .

17 Encoding level (#) – full level – select from the list.

1. Block of coded information.

The block contains coded data elements of a fixed length.

The data in these fields is determined by the relative position of the character, assuming the first character following the subfield identifier to be null. If this field is optional and the bibliographic agency does not provide the corresponding coded information, the field is omitted. If non-mandatory data is not used, its positions in the field contain the placeholder characters " | ".

100 General processing data.

The field contains fixed-length encoded data applicable to records of documents presented on any media. .

0-7 The entry date of the entry in the file is set automatically.

8 Publication date type - monograph.

9-12 Publication date1 -<>- year of publication of the document.

13-16 Publication date 2 -<>

17-19 Destination code - for adults, scientific - is set by default.

<у>-non-government publication - set by default.

21 Modified entry code<0>.

22-24 Cataloging language “rus” – set by default.

34-35 Title graphics (alphabet) "rus" - by default.

101 Document language.

The field contains encoded information about the language of the cataloged document, its parts and title, and also indicates the original language if the document is a translation. Mandatory

And 1 Translation indicator 0-document in the original language - by default.

$а - text language "rus" - by default.

It is repeated when the text is written in more than one language.

If the document is a translation, set:

AND 1 Translation indicator 1 - the document is a translation of the original.

$a - text language "rus";

$c - original language - select from the list.

102 Country of publication or production.

The field contains codes for one or more countries of publication or production of the document.

$a - country of publication "RU" - by default.

2 Block of descriptive information.

200 Title and statement of responsibility. Mandatory. Doesn't repeat.

The field corresponds to the area of the title proper GOST 7.1-84. The field contains, in the form and sequence determined by the Rules: Title proper, Parallel titles, Title information, Responsibility statement.

And 1 title as hotspot<1>is the access point. Default.

$a The title proper is the title of the article.

$e Information related to the title - continuation of the title. Repeats.

$f First information about responsibility - full name - is copied automatically from fields 700, 701 when adding this subfield. Filled in at the end of the record creation. Doesn't repeat.

$g Subsequent Responsibility Statement - Copied automatically from fields 702. Completed at the end of record creation. Repeats.

3 Note block.

320 Notes on the presence of a bibliography/index in the document.

The field contains notes about the reference apparatus (bibliographic lists, auxiliary indexes, etc.) available in the document. Optional. Repeats.

4 Record link block.

Each link field must contain data fields with embedded labels, indicators, and subfield identifiers that identify the document to link to. The field must contain sufficient data to identify the record (if one exists) of the document being cataloged to be associated with, or, if the record does not exist, to identify the document itself.

Record link technique:

Select the link field to be formed in the record navigator (with one click of the left mouse button). Tab to the Entry page of the Entry Editor. In the upper right window, select the source directory with which the connection is being established - "Main directory". Enter a search attribute (collection name). Functions available here simple search with value truncated on the left and right (use the * character). Click on the image of the binoculars. The associated entry can also be retrieved from the directory using the Directory Search window. After executing the query, view the retrieved records. To view complete record you can use the box at the bottom of the list. Select the line with the desired entry and double-click the left mouse button (or click the "Link entries" button). An inline entry for the document you are linking to will appear in the entry navigator.

The following field applies:

463 Physical unit level.

The field is used to identify a hierarchical relationship to a document at the level of a physically separate unit. The record being linked to has a physical unit level, and the record containing this field has an analytic, set, or subset level.

And 2 indicator notes<1>.

After the record is associated with the document, field 200 - Title and responsibility information and subfields $a, $b, Se are filled in automatically. Here we add the subfield $v "Volume Designation", where we put the pages of the article ourselves. The dot at the end is required.

The field is automatically filled -

210 Publication, distribution, etc.:

$a Place of publication, distribution, etc. -<М.>.

$c Name of publisher, distributor, etc. -<Либерия>.

$d Date of document, distribution, etc. -<>- year of publication of the document.

6 Topic definition block.

The block contains thematic data, both textual and presented in coded form, compiled according to the rules of various subject and systematization systems.

The value of fields 600-608 may be selected from authority/normative files.

Add the required field if it is not in the document template. Select the line with the name of the field (with one click of the left mouse button). In the upper right window "Value" select the rubricator in which the authoritative record with which the link is established is located. Enter a search term. Click the "Run Request" button or binoculars drawing. After executing the query, view the found records. Select the line with the desired entry and double-click the left mouse button (or click the "Link entries" button). An embedded authority record will appear in the highlighted box on the left side of the screen to which you are linking.

To do this, select the required field in the record navigator, use the “Tab” key or the mouse cursor to go to the “Value” page, in the current record value editor, use the keyboard to enter necessary information, which, when you press the "Enter" key, is transferred to the field.

600 Person name as subject heading (person). Optional. Repeats.

The field contains, in the form of an access point, the name of a person who is one of the objects of consideration in the document. Optionally, additional thematic formal, chronological and geographic information may be added to the person's name.

And 2 Way to enter the person's name<1>- default.

$bThe part of the name other than the initial input element is the author's initials.

610 Uncontrolled subject terms (keywords). Optional. Repeats.

The field contains, in the form of a hotspot, subject terms borrowed from non-controlled subject heading lists

I 1 Thematic term significance level<1>- default.

$a Topic term. If there is a built-in reference book, we take the term from the reference book. The directory represents a list of values. Selecting a value from the list is done by pressing the Enter key or by double-clicking the mouse. The "Reference" page has its own button bar with operations for adding new, editing and deleting reference items.

This field contains indexes of classification systems not used internationally, but with widely used printed tables.

LBC indices separated by a "+" sign are recorded in separate repetitions of field 686.

$a Classification index - take from the directory or type from the keyboard.

$2 System code "rubbk" - set by default.

7 Block of intellectual responsibility.

The block contains the names of persons and organizations that are intellectually responsible for the creation of the document. Intellectual responsibility extends to all personal and generic names and to organizations associated with the document, including publishers, if they require the creation of an access point

700 Name of person - primary intellectual responsibility (author).

The field contains, in the form of an access point, the name of the person with the primary intellectual responsibility (the first or only person in the header containing the name of the individual author). Mandatory if an access point is to be created in the name of the person with primary intellectual responsibility.

This field cannot be present in the same entry that has Organization Name - Primary Intellectual Responsibility field 710 or Generic Name - Primary Intellectual Responsibility field 720, since an entry can only have one primary intellectual responsibility access point.

And 2 - under<1>.

701 Name of person - alternative intellectual responsibility (2 and subsequent authors).

The field contains, in the form of an access point, the name of the person who has alternative intellectual responsibility. If the bibliographic record is to be displayed under the heading of an individual author, then the co-authors of the cataloged document, used as access points, have an alternative intellectual responsibility. If a bibliographic record is to be displayed under a title, then all individual authors of the document being cataloged, used as access points, have alternative intellectual responsibility. (If the bibliographic record is to be displayed under the heading of the collective author, then the individual author can only bear secondary intellectual responsibility - field 702).

Mandatory if an access point is to be created in the name of the person with alternative intellectual responsibility. It is repeated for each of the persons bearing alternative intellectual responsibility.

<1>.

$b Part of the name, except for the initial element, is the initials of the author.

After processing, the entry is stored in the directory, by clicking the left mouse button on the "Save entry" icon in the upper right menu, open the "Main directory" and copy the entry..jpg" width="179" height="112 src=">, clicking on "Print" icon, print the required number of cards. If necessary, edit the card manually. To switch to the editing mode, left-click in the place where the card is edited. In this case, a flickering cursor should appear in the card field. Further editing steps do not differ from working with any text editor.

Copying an entry.

The entry can be copied into the editor window (button https://pandia.ru/text/78/403/images/image006_20.jpg" width="19" height="25 src="> or the menu item "Delete Entry". This displays a window confirming the user's desire to delete the record.

Editing a post.

After connecting to the main server of the NPB BSPU, press the button "Select an entry from the catalog" Select the line "Main catalog" (double-click the left mouse button). Enter the search attribute of the publication (author or title). Click the "Run Request" button or the binoculars picture. After executing the query, view the found records, highlighting the required line by clicking the left mouse button. For a detailed view, press the "View record" button or double-click on the line with the left mouse button. To return to the "Search in the catalog" window, click the "Query" button. If the found entry fully matches the described document, click the "Edit Entry" button0 " style="margin-left:-39.6pt;

Current version 01/16/2004

Compiled by:, head. SBO NPB BSPU

Approved at a meeting of the Methodological Council of the NPB BSPU

Chairman of the Methodological Council

RUSLANA (Ruslan's database) contains comprehensive information about companies in Russia, Ukraine and Kazakhstan. You can use it to analyze a specific company, as well as find and analyze companies with a specific profile. RUSLANA is represented with software new generation from BvD - simple and easy to use.

Benefit for you

What information does RUSLANA contain?

Financial indicators of the company, detailed format, data for the last 10 years
Leaders and contacts
Activity code and trade description
Exchange data on public companies
Detailed corporate structure, search for companies with the same owner
Shareholders and subsidiaries
Business news by company
M&A deals and rumors about them

Ruslana is perfect solution for transfer pricing specialists, marketers, marketing and sales specialists, professionals in the field of M&A, credit risks and compliance.

Using the Ruslana product, you will find the necessary information about the company you are looking for and will be able to evaluate the given company.

Search by more than 100 criteria - You can create searches from several steps, compare data over the past years. The product interface allows you to combine a large number of search criteria and use a logical search (and, or, and not). After selecting a group of companies, you can compare them with each other, create graphs and tables
Thanks to the flexible interface of the product, you can use Ruslana for a variety of research projects, including: detailed financial and credit risk analysis, corporate finance, venture capital and M&A research, sales and marketing performance studies, feasibility studies, data collection for various campaigns, for academic purposes
You can create your own metrics, calculate sector average, change the report format and customize data structure, make comparisons and estimates, export data(Excel, Access...)
The Addin function allows you to analyze data from Ruslana in Excel / Access, so you can compare your own data with data from our database (they are updated daily), thereby expanding your own database
You can also conduct transfer pricing analysis
credit risk analysis department
department of corporate finance, M&A and consulting companies
marketing department
educational and scientific institutions

Automated Library and Information System

"RUSLAN"â

automated workplace

“PACKAGE/CATALOGUE”

Version 3.7.x.x

SYSTEM PROGRAMMER'S GUIDE

St. Petersburg, 2007

Introduction

Computer program Ruslan Acquisition/Catalogue Automated Workstation (AWP) has some customization options and tools for technical support. This guide is intended for personnel with basic training in the field of maintaining MS Windows applications and providing technical support for ABIS Ruslan in the organization.

The Guide contains installation instructions and a description of the AWP core settings. For some questions, the Guide contains links to the relevant documentation on individual modules, subsystems and external applications used by the workstation (print service, on-screen / virtual keyboard, classification index module, marc record converter, MS Office package, Internet Explorer). In addition, a number of AWP parameters are directly or indirectly related to the corresponding settings of the system server, which are set using the Ruslan Administrator AWP. In this case, you should refer to the Administrator's Guide for the server part of ABIS “Ruslan”.

The following groups of AWP settings can be distinguished:

1) parameters of configuration files (*.ini ),

2) settings for the used formats of the MARC family (marc .* files),

3) print service output form templates (*.ini , *.tpl , *.xls , *.dot ),

4) post templates in MARC / ISO2709 format (*.ptt ),

5) settings on-screen keyboard(*.xml ).

1. Installing and uninstalling the program

1.1. Initial installation of the program

The initial installation of AWP is carried out using the supplied distribution kit catwbful.rar.

The distribution also comes with the following documentation:

-catwbmanual.rar(a set of files by sections) - User's Guide,

- catwb_admin.htm- System Programmer's Guide (this document).

For the initial installation of AWP, you need to expand the archive catwbful.rar, run the installer \DISK 1\setup .exe and go through all the steps of automatic installation.

During the installation process, the installer will prompt the user to select a folder for installing AWP (by default, WITH:\programFiles\RuslanCatalog) and the name of the item in the system menu (default - RuslanCatalog). We recommend that you accept the default values. As a result of the installation, the Installer will automatically create all the folders necessary for the work of the Workstation (in the working folder of the Workstation), register the required components of the Workstation in the system, and install all configuration files with default settings.

After completing the above installation steps, the workstation is completely ready for operation. Further, specialized user settings are required (server address, organization code and name, lists of values, other local settings and settings).

1.2. Uninstalling a program

Removing the AWP program from the computer is done using MS Windows tools:

Control Panel - Add/Remove Programs section - Ruslan Catalog program.

1.3. version update

Users connected to the System Maintenance(TO), receive updates of AWP versions as they are released. To update the version, it is enough to replace the file whose update is provided. As a rule, an update is provided executable file catwb.exe and/or format settings database files marc.*.

It should be noted that when updating the AWP version, changes in the INI configuration files may be required. Insofar as INI files are configured and maintained by the user themselves, changes must be made to the current versions of the files used by the user. The description of the new parameters is given in the messages of the Maintenance System at the time of the release of updates and is reflected in subsequent versions of this Manual.

The MARC format settings database is maintained centrally - by the TO System. New versions of DB formats are installed in the usual way - by simply replacing the marc.* files (six files in total).

Updates to output form templates are provided as new versions of *.tpl template files (\Documents\Scripts folder). Also, it may be necessary to add/replace the corresponding MS Office document template files: *.xls, *.dot (\Documents\Templates folder) or print settings files (\Documents\Settings folder).

2. Working with parameters of INI configuration files

The main parameters can be set from the AWP window “ Settings”, which is called from the menu Directory-Settings. The window has several pages containing elements for editing the settings of various groups. But if necessary, access to the parameters can be obtained directly - in the INI configuration files, using any text editor.

INI files can be stored either in the current (working) directory of the AWP, which is selected at the time of installation of the distribution kit (the default directory is WITH:\programFiles\RuslanCatalog), or in the directory specified in the parameter IniDir App .ini file. This file is always read from the current directory. Using a Parameter IniDir to indicate network folder allows you to use shared files configurations for multiple jobs.

All files with the INI extension have the same format, corresponding to the format of MS Windows initialization files. The files contain the values of the parameters - each in a separate line of the form:

Parameter name = Parameter value

If the parameter value is an array, then all array elements are listed in one line separated by commas. All data must be entered in Win 1251 encoding.

Parameters are combined into groups according to their purpose. The name of each group appears on the first line in square brackets. Start next group automatically means the end of the previous one. The order of the groups in the file and the parameters within the group does not matter and can be arbitrary.

The composition and purpose of AWP configuration files are described below.

2.1. Configuration file a pp.ini

App.ini- a file containing the current settings of the workstation, usually unique for each workplace. These settings are saved automatically during the user's work with the workstation (the last state of windows, etc.). Most of them do not require manual configuration. The most significant parameter groups are described below.

Group/parameter name	Possible values				Description
	General settings
					Directory for storing configuration files. Default is empty (working directory)
DicControl					Specifies whether to monitor the MARC directory of the entry. Checks that each bibliographic entry complies with some requirements of ISO 2709.
	MARC Download Options
ToLoad	Array of strings RUSmarc, USmarc				List of format names of the MARC family, which are loaded when the AWP is started. It is recommended to specify for loading only those formats, the processing of which is required in the record editor window.
ToLoadBib	0/1				Specifies whether to load bibliographic formats from those specified in the ToLoad list
ToLoadAuth	0/1
	Entry: Directory search
	Current window state settings Z39.50 catalogs
	Current window state settings
	Current state settings of the post editor window
	Current parameters of the state of the save record to file window
	Window settings Entry: Directory search
NewListQ1 NewListQ2 NewListOp			Job RPN expressions search query to generate a list of new arrivals (special mode of the window Entry: Catalog Search-List of New Arrivals). You can define 2 expressions Q 1 and Q 2 combined with the logical operation Op . By default, the request is specified by the date range of receipt (account opening date). Dates are set by the user in the format YYYYMMDD in the first and second search fields on the page Simple search. Filtering of invoices with negative numbers (retroconversion) and invoices that have not passed the full processing cycle (status<3)
SortCaseSensitivity	0/1		Whether or not to distinguish between upper/lower case characters when sorting in a list of search results
SortLinkTitle	0/1		Whether or not to take into account data in built-in fields when sorting by title (Rusmarc 46X ->200a ,h ,i )
	Window settings Copy entry to directory(selection of directories to add new entries).
	0 /1		Enables the mode of automatic replacement of records with new ones, when the keys match (001). It is used, as a rule, for batch updating of directories.
	0/1		Enables automatic check mode on the server new record for duplicates in the specified directories.

	Account processing
	Current window state settings Act processing
	Current window state settings Processing a subscription request
	Current window state settings
	Current window state settings Book order processing
Pattern.File			Full name of the template file (.* ptt) to create order identification records
	Current window state settings Directory. Each directory has its own group of parameters. ID this is the numeric identifier of the directory in the system
	Current window state settings inventory book
	Current window state settings Summary ledger
	Current window state settings
rsChar	Number ( 29 )			Decimal code of record separator character
fsChar	Number ( 30 )			Field separator character code
ssChar	Number ( 31 )			File subfield separator character code The above options are used to load marc records from files with non-standard delimiters. The default is to use standard separator characters (see ISO 2709)
	Settings of built-in marc-records converter (see converter description)
	0 /1	Add characters \"????\" to the beginning of an unknown subfield
	0 /1	Leave unknown subfields in a record
	0 /1	Convert 09X group fields (as is)
	0 /1	Convert 8XX group fields (as is)
Op16	0 /1	Convert 9XX group fields (as is)
Op32	0 /1	Convert 5XX group fields to 390 field if there is no exact match (only for USmarc ->RUSmarc )
Op64	0 /1	Convert with translation (removal) of constant expressions (not used)
Op128	0 /1	Convert field 852 to field 999 (instead of 899)n

2.2. Configuration file config.ini

In file config.ini the main settings of the AWP are stored. These settings are usually static and are set at the time of initial system configuration.

	General settings
BarCodeMask		Specifies the barcode value mask. Sh/K must be a number whose bit width is given by the number of digits 9 before the sign “;” (9999999999;1;0)
ScanDic	0/1	Enables the mode of using directories as indexes Scan Service Z 39.50 (optimal mode 1)
Separators	, .:;()-=""?! <>\/#§№ 1234567890	A string of characters that should be treated as word separators when checking valid character combinations within a word in the post editor (see the CheckingUp parameter)
	Parameters (common for all marc formats) used to set default values in the marc format settings (see the description of the MarcConfig utility). Below are examples of parameters.
Organization		Organization code in English
Organization_en		Organization code in Russian
	marc record linking mechanism settings
	Array of numbers	List of field tags copied to 4xx fields when automatically linking records in Unimarc-like formats
		List of field tags copied to 4xx fields when automatically linking records in Usmarc-like formats
Bills Acts Subscr orders DDir Gens AllBibDb tpush nlr_sh	Service database name settings. All values must be the names of the databases configured on the server.
	Bills		Database of accounts (acceptance certificates)
	Acts		DB of acts on writing off (exclusion from the fund)
	SubscrP		Subscription request database
	OrderP		book order database
	DDir		Directory description database
	Dir		Directory database
	line (Dir)		Database of inventory number generators directory
	ucat		Virtual database that unites all bibliographic databases of the system
			Relationships of subject codes and corresponding authoritative databases
			A group of parameters for defining specific DB accounts for individual bib.DBs. By default, all distributions go to accounts in the Bills database (see setting above)

Parameter group for defining a list of specialized samples on the server, usually for collecting statistical data

List of strings - values to edit the subfield Issuance restrictions On the page Inventory number($999)

Window settings Post editor

DicDataRepeatToField

0 /1

When working with directories, add automatically new fields or repeat subfields in one field

AuthDataRepeatTo Field

0/1

When working with AF, automatically add new fields or replace subfield values in the current field

CheckingUp

0/1

Enable the editor to automatically check for valid combinations of characters in one word as you type

RemoveInvNumsO nCopy

0/1

Automatically delete inventory numbers when copying a record in the editor (fields 999)

GenerateASign

0/1

ASignFileName

asigns3.ini/

asigns2.ini

Valid from version 3.6, points to Khavkina's table file (three-digit or two-digit). Specified file should be in the working folder of the AWP.

GenerateSysIndex

CheckEmptyLink

Enable checking for empty subfield values in link fields (4xx) when automatically linking records

show class

0/1

Enable a specialized component for working with classification indices

ShowVK

0/1

Enable the “Virtual Keyboard” component

ShowCopyBtn

Show "Copy to directory" button

Spelling Up

Enable automatic spell check of text fields (Russian language) – option compatible with MS office up to version 2000 inclusive .

Voc Name

Full file name

Path to the MS Office Russian language dictionary file (used up to version 2000 inclusive).

DicName

Full file name

Path to the MS Office user dictionary file (used up to version 2000 inclusive).

CheckDoubletBarCode

Enable automatic barcode re-entry control (not only for fields 999 of the record being edited, but also for all bibliographic databases included in the group database specified in the AllBibDb parameter)

SubFilterAnalit

Service parameter that includes an additional filter of analytical records when searching for issues of periodicals received by subscription.

List of values for a field Note in the window Act processing

List of values for a field Cause write-offs in the window Act processing

List of values for a field Source of income in the window Account processing

List of values for a field Accompanying documents in the window Account processing

List of values for a field Note in the window Account processing

List of all possible account state values

Values of the status of an account opened by a user of this category

Values of the status of an account closed by a user of this category

Values of the state of the account ready for processing by the user of this category

Values of the state of the account that has passed the full cycle of processing

List of all possible subscription request state values

List of values for a field A source in the window Processing a subscription request

List of values for a field Payer in the window Processing a subscription request

List of values for a field Publication type in the window List of identification records

List of all possible book order status values

List of values for a field The supplier in the window Order Processing

List of values for a field Customer in the window Order Processing

List of values for a field Accompanying documents in the window Order Processing

List of values for a field Source of financing in the window Order Processing

List of storage sigle

List of indexes for the "Classification part of the cipher" field in the record editor window on the accession numbers page

Query parameters for retrieving records in the window inventory book

List of storage sigls for a window Inventory book. Used to form books separately by sigs or groups of sigs (several sigs separated by commas).

List of field values Format to set a query to retrieve records in a window inventory book

List of values for the prefix field to specify a query to retrieve records in the window inventory book

List of suffix field values for specifying a query to retrieve records in a window inventory book

List of values for a field Recipient. Used in order and subscription windows.

List of possible values for a field Bibliographic level in the directory search window.

SubjectHeading

personal name

corporate name

GeographicName

Header and attribute type association options (default) to find matching authority records on the page Recording in the editor window.

Search attribute

personalia

Collective name

Geographic name

Parameters for linking header types and authority database names to search for authority records on a page Recording in the editor window. For one header type, you can specify several databases separated by commas.

List of specialized sets of search attributes for various authoritative databases on the page Recording in the editor window.

List of specialized sets of scanning attributes (browsing indexes) for various authoritative databases on the page Search records in the editor window.

List of specialized attribute sets for sorting authoritative databases on a page Recording in the editor window.

converter settings. Enable/Disable different directions for converting entries in the editor.

Record template names used by default in various windows.

, Rusmarc /Authority , Usmarc , Unimarc . There is a separate configuration file for each format (rusmarc .ini , rusmarcA .ini , usmarc .ini , unimarc .ini ). The file stores static format settings: lists of indicator values, subfields of coded data fields, and parameter values. All listings are as follows:

[list title]

Value1 = Noteto value1

Headings of lists of values can be arbitrary (in the Latin alphabet). But they must correspond to the designations that are entered in the database of formats. By default, titles are generated automatically according to the designations of the corresponding elements of the record.

For field: [field tag]

For a subfield: [field tag. Subfield ID]

For indicator: [field tag. i 1] or [field tag. i 2]

For part of code field: [field tag. Subfield identifier. Position]

For marker

Comments inside lists that are invisible to AWP can be entered on lines starting with the sign ; (semicolon).

Spaces are marked with #.

The parameter group contains default codes:

Organizations in Russian and English (Organization, Organization _ru),

The code of the local subject system (SubjectSystem ),

Encoding level of the entry (CodeLevel ).

List of codes of organization- holders of funds.

List of values for the note subfield of the storage unit 999$x.

List of intellectual responsibility codes and their corresponding text notes for generating subfield values 200 $f , $g (Rusmarc ).

List of field tags for connecting authority records in the form:

bibliographic record field tag=list of valid authority record field tags

For instance:

For the rusmarcA.ini file, the corresponding list will look like:

For instance:

200=600,700,701,702

210=601,710,711,712

Standard codes for language names.

Standard country name codes.

Codes of organizations (departments) to indicate the labels “Recommended”.

Character sets.

Accepted abbreviations for city names.

Alphabets.

Codes of intellectual responsibility.

Cataloging rule codes.

Codes of thematic systems (subject subject systems, rubricators, thesauri).

Classifier of directions of higher education.

Classifier of specialties of higher education.

Author's mark table (for the 999$i subfield). It is allowed to use two- or three-digit Khavkina tables ( deprecated - since version 3.6 a separate table file is used - signs 2.ini or signs 3.ini ).

Organization storage sigils.

Access schemes to electronic documents by URL.

Reference book of BBK indexes.

2.4. Attr config file (attr .ini )

File attr.ini is intended for storing sets of attributes, a list of formats, server options used in AWS to search and retrieve records using the Z 39.50 protocol.

All attributes are grouped into sections and are specified as:

[set name]

Attribute code1 = Attribute name1

The name of the attribute determines how this attribute will be displayed in the list of attributes of the window for searching for records in the directory.

The main search is the standard set of attributes BIB -1 (ANSI /NISO Z 39.50-1995). It is broken down into several attribute groups to indicate various search query parameters.

Search attributes (terms).

This set is extended by several non-standard attributes, which are used by the workstation to access specialized data (which, as a rule, have a local purpose). Non-standard attributes are listed at the end (>9000).

Attributes that define the type of relationship between the search term and its value (>,<,= и.т.д.).

Set a constraint on the position of the given term in the data field.

Define the structure of the data entered in the search term field.

Specify the type of term data truncation.

Define additional conditions for the completeness of data in the term.

Used to search for records in external sources.

List of record formats for specifying a search query.

Z39.50 Server Options List (ANSI/NISO Z39.50-1995).

User guide

Version 3.8.1

annotation

This document provides information about the purpose of the Reader's Workstation program and the conditions for its use. The sequence of user actions that ensure the successful execution of the program is described and illustrated in detail.

Chapter 1. Purpose of the program

The program is designed to provide remote users with access to Z39.50 service resources. Remote users can be any users of the Web server on which the Reader Workstation operates. Z39.50 service resources can be various remote databases (bibliographic, full text, ISO delivery request databases). Thus, the program is an intermediate link in a multi-link information system that provides users with the following features:

search for bibliographic, full-text information, information about orders, information about the location and availability of a document in remote databases with the ability to eliminate duplicates, navigate through search indexes and automatically expand the query using thesauri and authority files;

ordering a document (copy) according to its description;

checking the status of an order;

displaying a list of documents received for temporary use.

In other words, the program is with a Web-based user interface. Therefore, the gateway is accessed via .

Chapter 2. Program Execution Conditions

The prerequisites for running the program are:

Preferred, but not mandatory, conditions for the implementation of the program are:

Chapter 3 Program Execution

Working with the program consists of sequential execution of the following steps:

Steps 2-4 can be performed multiple times within a single session, as The search is generally an iterative process.

The ability to perform step 4 depends on the method of initialization (requires user authentication) and on the capabilities of a particular .

The ability to navigate through search indexes is determined by the capabilities of a particular .

3.1. Initialization

There are two modes of establishing a connection with : with user identification and without it. In the first case, the user must fill in the fields of the form offered to him for identification: user name and password. The appearance of the form is determined by the developer of the Web server and, generally speaking, may differ from the example given in . However, the requirement for the user to specify a name and password is fundamental. When entering a password, depending on the Web agent used, the data is not displayed or is displayed as placeholders.

Figure 3-1. An example of a form for identifying a user of a Z39.50 server

In non-user authentication mode, the connection is established by activating the corresponding link. Links to various sources of information may be provided by the Web server developer on one or more pages.

If the connection is successfully established, the user is presented with a request form and can proceed to step 2 (see ). If initialization fails for some reason (for example, the server is currently unavailable or the password is incorrect), the program will issue a diagnostic message indicating the reason. In this case, the user can try to eliminate the causes themselves (for example, check the case of the entered characters and enter the password again), try to connect to the source later, at another time (if the server is unavailable), or contact the administrator for help.

3.2. Search

The type of the search form offered to the user after successful initialization is determined by the developer of the Web server and the capabilities of a specific Z39.50 source (access points, logical operators, record presentation forms, navigation and deduplication capabilities). An example of such a form for searching bibliographic information with the names of controls is shown on .

Figure 3-2. Search form example and controls

	Access point list
	List of databases
	Request field
	List of qualifying attributes
	List of operators
	Document location information switch
	sort switch
	List of sort keys
	List of record formats
	Query Expansion Switch
	Deduplication switch
	List of thesauri
	Record count field
	Search button
	Search index view button

3.2.1. Request fields

The search is carried out according to the words specified by the user in request fields. The order in which the fields are filled in does not matter. The distinction between uppercase and lowercase letters, or lack thereof, is determined by the particular . Most servers do not recognize these letters. You can enter multiple words in one field. Words are separated or not separated from each other according to the rules of the natural language in which the search is performed.

3.2.2. Access points

The meaning of the request in a particular field is determined by the access point selected from access point lists. The set of access points is determined by the developer of the Web server and the capabilities of a particular . Access point lists can be of two types - with the ability to select only one item and with the ability to select multiple items. The method for selecting multiple items from the second kind of lists is determined by the user's operating system and the user's Web agent. If several elements are selected, then it is considered that the "logical OR" operation is performed on these elements.

3.2.3. Qualifying attributes

You can also refine the meaning of the query with qualifying attribute list. For example, multiple words can be interpreted as a phrase when word order is important and an exact search is required, otherwise you can select "Word List". The set of qualifying attributes is also determined by the developer of the Web server and the capabilities of the particular . When searching by author's name, it is possible to use the "Normalized name" qualifying attribute. In this case, the name should be entered as follows: surname, comma, initials (for example, "Ivanov, A.I.").

3.2.4. Entering dates

Dates other than the year of publication should be entered in accordance with 7.64-90 in the format YYYYMMDD (for example, "19970328" - March 28, 1997). The year of publication must be entered in the format YYYY, while some servers require the selection of the qualifying attribute "Year".

3.2.5. Logical operators

If requests are entered into several fields, then these fields are subject to logical operations selected by the user from operator lists located between the filled fields.

3.2.6. truncation

You can search by the initial and final letters of words, as well as by letters from the middle of the word (respectively, the truncation operations on the right, left, right and left). To do this, use the "*" character, which can only be placed at the beginning or at the end of the request field. If "*" is at the beginning of the query field, then the search is performed by the final letters of the word. If "*" is at the end of the query field, then the search is performed by the initial letters of the word. If "*" is at the beginning and at the end of the query field, then the search is performed by letters from the middle of the word.

If a truncation operation is applied to an expression that has a "Word List" qualifying attribute, the search will be performed on the beginning, end, or middle letters of each word. If the operation is applied to an expression that has the "Phrase" qualifying attribute, then the first or last word is truncated.

3.2.7. Examples of filling in request fields

Examples of correct and incorrect filling of request fields and selection of qualifying attributes are given in the tables and , respectively.

Table 3-1. Examples of correct filling of request fields

Request field	qualifying attribute	A comment
neuron set*	Word list	All documents will be found in the description of which there are words starting with " neuron" and " set" - for example, if the title contains the words " neuron nyh set her", " neuron nye set and", " neuron but- set ev", " set and on binary neuron Oh"
neural set*	Phrase	All titles containing the word "" will be found. neural" followed immediately by a word beginning with " set" - for example, if the title contains the phrase " neural set and"
* work tion	Word list	work" and " tions" - for example, if the title contains the words "about work inform tions", "once work compass method tions "
*working information	Phrase	All titles containing words ending in " will be found. work" and immediately followed by the word " information" - for example, if the title contains the phrase "about information processing "
works form techno	Word list	All publications will be found, in the description of which there are words that contain the letter combinations " works ", "form ", "techno" - for example, if the title contains the words "time works ka in form rational techno logic" or "time works ka super techno logical modeling processes based on de form rational parameters"

Table 3-2. Examples of incorrect filling of request fields

3.2.8. Record Forms

The preferred form of representation of the found records is selected from list of record submission forms. The list is defined by the developer of the Web server. The ability to present a record in the required format is determined by the specific . If the records cannot be represented in the required format, then the user receives either a diagnostic message or records in one of the supported formats.

3.2.9. Number of records to retrieve

V record count field the user has the ability to specify the portion size of the retrieved records. The time to wait for a response with search results may depend on the value of this parameter. The actual number of entries in a chunk is determined by the specific .

3.2.10. Elimination of duplicates

With help deduplication switch the user has the ability to control the process of displaying duplicate records. If the switch is in the "On" position, then the operation of deduplication is performed on the found records - instead of several records that are considered doublets from the point of view of a particular one, one record is shown - a representative. This operation is quite resource intensive, so it is not performed if there are a large number of found records. In this case, it is possible for the user to receive an appropriate diagnostic message; all found records are shown.

3.2.11. Sorting

With help sort switch and sort key list the user has the ability to set the sorting criteria for the found records. Sorting is done in ascending order of key values, case insensitive.

3.2.12. Query expansion

With help request expansion switch and list of thesauri the user has the ability to control the automatic expansion of the query using thesauri and authoritative databases. This feature is recommended to be used only in cases where the number of found records is unacceptably small. This may reduce the accuracy of the search.

3.2.13. Mode change

With help mode change links the user has the ability to change the mode of operation with the program. The operating modes differ in the number of controls in the search form and, accordingly, in the available functionality. The nomenclature of operating modes is determined by the developer of the Web server.

3.2.14. Calling the Virtual Keyboard

With help virtual keyboard call links the user has the ability to call up a dialog menu designed to enter characters from various alphabets, the input of which directly from the keyboard may be difficult or impossible. The selected character goes to the end of the current request fields. How to use the Virtual Keyboard is described in the corresponding User's Guide.

3.2.15. Calling the Dialog for entering classifiers (rubricators)

With help links to call the Dialog for entering classifiers (rubricators) the user has the ability to call a dialog menu designed to navigate and select the value of a search term from various classifiers (rubricators). The selected value is included in the current request field. The procedure for working with the Dialogue for entering classifiers (rubricators) is described in the corresponding User Guide.

3.2.16. Calling up help

With help help buttons the user has the opportunity to go to a document describing the procedure for working with the program or to any other document.

3.2.17. Executing a search query

The search query is executed after the corresponding impact on search button. If the search is successful and records are found, then the user receives information about the records found and proceeds to step 3 (see ).

If the search is successful, but no records are found, the user receives an appropriate message and can proceed to compose a new request by returning to the page with the request form. The return is carried out by means of the user (navigation control button or key combination) or through the corresponding navigation elements presented on the page with search results.

If the search is not successful, the user receives diagnostic messages explaining the reasons for the failure. In this case, the user can also proceed to compose a new request. If the number of diagnostic messages exceeds a certain level defined by the Web server administrator, then these messages are not displayed immediately, but can be displayed by activating the appropriate navigation elements provided on the search results page.

3.2.18. Executing a query to view the server's search indexes

The request to view the search indexes is executed after the corresponding impact on browse index button. Generally speaking, browsing capability is determined by the Web server developer and the capabilities of the particular .

If the browsing is successful, then the user receives a list of search terms contained in the index corresponding to the selected access point. The list begins with the term that is closest in the lexicographic sense to the query. The list also indicates the approximate number of entries containing the particular term.

Depending on the setting of the Reader Workstation, the browsing results are displayed either in a new window or in the current window. In the first case, when the hyperlink corresponding to the selected term is activated, the value of the term is passed to the request form. In the second case, when the hyperlink is activated, records are searched for this term. If the search is successful, the user proceeds to step 3 (see ).

The user is also given the ability to navigate through the search index using the appropriate navigation elements provided on the browsing results page.

Figure 3-4. Example of viewing search results - bibliographic records in short form

Figure 3-5. Example of viewing search results - bibliographic record in full form

3.4. Ordering a document according to its bibliographic description

The document order stage consists of several stages, the number of which depends on the order properties specified by the user. At the first stage, the user is shown a bibliographic description of the document and is offered the opportunity to supplement it with information about a particular document (volume, issue, number), because description can be made on a set of documents. Such additions are optional, but may affect the result of order processing. In addition, the user is prompted to select one of the four forms of working with a document from the list: "Receiving a document for temporary use", "Receiving a copy of a document", "Receiving a certificate about the location of a document", "Receiving a certificate about the cost of delivering a document". Upon completion of the selection, the user can continue the checkout by activating the "Continue" button.

If there is information about the location of the document, the user is prompted to select the preferred holder (organization, department) by activating the appropriate switches. An example of starting a document order is shown on .

Figure 3-6. Document order - stage 1

3.4.1. Receipt of a document for temporary use

When ordering a document for temporary use, at the 2nd stage of ordering, the user is shown a bibliographic description of the document. In addition, if at the first stage of placing an order, the user specified additional information about the document (volume, issue, number), he is given the opportunity, if necessary, to make changes to this information. Also, the user is given the opportunity to choose the method of processing the order if it is impossible to immediately provide him with a document. One of three order processing methods is selected: "Put the request in the queue", "Do not queue the request", "Act in accordance with the rules of the library". An example of the corresponding form is given on . Upon completion of the selection, the user can continue placing an order by activating the "Order" button. After that, he is shown information about the order made (see).

Figure 3-7. Ordering a document for temporary use

3.4.2. Get a copy of a document

When ordering a copy of a document, at the 2nd stage of ordering, the user is shown a bibliographic description of the document. In addition, if at the first stage of placing an order, the user specified additional information (volume, issue, number) about the document, he is given the opportunity, if necessary, to make changes to this information. The user is also given the opportunity to specify specific pages of the document to be copied. Completing the corresponding field is optional. The user also has the option of specifying the preferred form of the copy (eg, photocopy or electronic copy). The list of possible copy forms is determined by the Web server developer. An example of the corresponding form is given on .

Upon completion of the selection, the user can continue the checkout by activating the "Continue" button. In this case, the user proceeds to the third stage of placing an order. At this stage, he is shown a bibliographic description of the document. In addition, if at the second stage of placing an order, the user indicated specific pages to be copied, then he is given the opportunity, if necessary, to make changes to this information. Upon completion of the selection, the user can continue placing an order by activating the "Order" button. After that, he is shown information about the order made (see).

Figure 3-8. Ordering a copy of a document

3.4.3. Get help

When ordering information about the location of a document or the cost of delivering a document, at the 2nd stage of placing an order, the user is shown a bibliographic description of the document. In addition, if at the first stage of placing an order, the user specified additional information (volume, issue, number) about the document, he is given the opportunity, if necessary, to make changes to this information. An example of the corresponding form is given on . Upon completion of the selection, the user can continue placing an order by activating the "Send request" button. After that, he is shown information about the order made (see).

Figure 3-9. Ordering a document location certificate

Figure 3-10. Order result

Chapter 4 Operator Messages

4.1. Initialization

The messages that the user can receive during the initialization phase, the meaning of these messages and the user's actions are presented in.

Table 4-1. Messages during the initialization phase

Message	Description	User Action
Network off	It is impossible to establish a connection with a specific one due to its unavailability	Try to establish a session again, or
Network unavailable
Timeout when trying to connect
Server is not available
Missing route to server
Invalid information - server not found or not responding
Reliable information - server not found	The server specified in the Reader Workstation configuration does not exist, or the name service is not functioning properly	Contact the web server administrator with a description of the problem
The name is valid, but there is no record of the specified type
fatal error	Unable to link to a specific one, most likely due to a bug in the Reader Workstation software	Contact the web server administrator with a description of the problem
The server closed the connection unexpectedly	unexpectedly closed the session, most likely due to an error in the server software	If possible, contact the software developers with a description of the problem
Can't get an answer	Unable to establish a session with a specific one, most likely due to an error in the server software
Unable to send request
Received an invalid response from the server
Received an unexpected response from the server
Server denied access	Not enough permissions to work with a specific	Check if the username and password are entered correctly. If necessary, enter these parameters again. In case of failure, contact the administrator.

4.2. Search, view search results, order a document

Messages that the user can receive at the stages of searching, viewing search results, ordering a document, the meaning of these messages and user actions are presented in.

Table 4-2. Messages at the stages of searching, extracting, ordering a document

Message	Description	User Action
Permanent system error	cannot perform operation	If possible, contact the administrator with a description of the problem
Temporary system error	temporarily unable to perform the operation	Try the operation later
Unsupported Search	User-specified search expression could not be processed	Reformulate the request
Search expression consists of stop words only	unable to complete search query	Reformulate the query, excluding stop words from it
Too many words		Reformulate the query, reducing the number of words in it
Too many logical operators		Reformulate the query by completely clearing some fields
Too many truncated words		Reformulate the query, minimizing the number of truncated words
Truncated words are too short		Reformulate the query by increasing the length of the truncated words
Attempt to retrieve a non-existent entry
System error while fetching records	can't represent found record	If possible, contact the administrator with a description of the problem
The specified combination of databases is not supported	cannot perform operation on specified databases	Reformulate the query by reducing the number of selected databases
Search results no longer exist - deleted by the server	unilaterally removed search results, possibly due to lack of resources	Search again
Search results are still being generated	received a request to retrieve records at a time when the search has not yet completed
One of the specified databases is locked	cannot perform an operation on one of the specified databases
The specified result set does not exist	cannot present entries without first performing a search	If possible, contact the Web server administrator with a description of the problem
Resources exhausted - no result		Search again later or contact the Web server administrator with a description of the problem
Resources exhausted - unpredictable partial result available		Continue work. If the result is unsatisfactory, quit the job and try to resume it later
Resources exhausted - valid partial result available
(Unspecified) error	unable to perform operation for unknown reason	If possible, contact the Web server administrator with a description of the problem
No access	Denied access to a database or record due to a lack of appropriate user permissions
Record not set to abstract format	can't submit entry	If possible, contact the Web server administrator with a description of the problem
Request type not supported
Bad request	cannot complete the search request because he is incorrect	Reformulate the request or contact the Web server administrator with a description of the problem
Database not available	cannot perform an operation on a specific database	Perform the operation again later
Unsupported operator	does not support searching using this operator	Reformulate the query to exclude the unsupported operator from it
Too many databases specified	cannot complete the operation due to lack of resources	Reformulate the query by reducing the number of databases
Too many search results generated	cannot complete the search request due to lack of resources	If possible, contact the Web server administrator with a description of the problem. Quit and try to resume later
Unsupported attribute type	unable to complete search query	If possible, contact the Web server administrator with a description of the problem
Access point search not supported		Reformulate the request using a different access point.
Unsupported term value for this access point		Reformulate the query using a different form of term specification
Access point not specified		If possible, contact the Web server administrator with a description of the problem
Unsupported relation attribute	unable to complete search query	Reformulate the query using a different relation attribute. If possible, contact the Web server administrator with a description of the problem
Unsupported structure attribute		Reformulate the query using a different structure attribute. If possible, contact the Web server administrator with a description of the problem
Unsupported position attribute		Reformulate the query using a different position attribute. If possible, contact the Web server administrator with a description of the problem
Unsupported truncation attribute		Reformulate the query using a different truncation attribute. If possible, contact the Web server administrator with a description of the problem
Unsupported attribute set	cannot complete the search request due to an error in the gateway configuration	If possible, contact the Web server administrator with a description of the problem
Unsupported Attribute Combination	unable to complete search query	Reformulate the query using a different combination of attributes.
Invalid search expression		Reformulate the request or contact the Web server administrator with a description of the problem
Incorrect term value for this access point		Reformulate the request
Only zero scan step is supported	can't complete search index lookup request due to an error in the gateway configuration	If possible, contact the Web server administrator with a description of the problem
Specified view step size is not supported
Not enough permissions to perform the operation	refused to perform the operation due to lack of appropriate permissions from the user	Contact the Web server administrator with a description of the problem or continue working
Defunct database	cannot complete the request due to an error in the gateway configuration	If possible, contact the Web server administrator with a description of the problem
Database access denied	denied access to the database, possibly due to a lack of appropriate permissions for the user	Contact the Web server administrator with a description of the problem or continue working
Unable to present the entry in the required form	cannot present the entry in the required format	Choose a different post format
Unsupported recording format	cannot present the entry in the required format	Choose a different post format
Service not available for this database	cannot execute a query for a specific database	Choose another database
Entry deleted	In the time interval between searching and retrieving the record, it was deleted	Continue with the program
SQL error	cannot perform operation	If possible, contact the developers with a description of the problem
Quota exhausted	The user can no longer send new orders to the system	Cancel unnecessary orders, or contact the administrator Z39.50 servers CAE Common Application Environment css Cascading Style Sheets HTTP Hypertext Transfer Protocol HTML Hypertext Markup Language IEC International Electrotechnical Commission ILL Interlibrary Loan Machine Readable Cataloging TCP/IP Transmission Control Protocol/Internet Protocol GOST State standard