About the Profile

The Profile

• Previous Releases

The Maintenance Agency

Resources

5.C. Functional Area C: Cross-Domain Search and Retrieval

Functional Area C addresses the requirements for effective cross-domain searching of networked resources including library catalogues, government information, museum systems, and archives. Three Conformance Levels are identified (0,1,2). Functional Area C exploits searches defined in Section 5.A.0. Functional Area A: Level 0 Search and Retrieval and Section 5.A.1. Functional Area A: Level 1 Search and Retrieval to enable early adoption of a cross-domain searching approach. Conformance Levels 0 and 1 requires the use of the bib-1 Attribute Set.

To address retrieval requirements in a cross-domain context, the profile requires SUTRS and XML for basic data interchange, The XML record syntax will be used with a Document Type Definition (DTD) for Dublin Core Simple. Retrieval records will be cast in the 15 basic Dublin Core metadata elements, marked up in XML using the DTD found in Appendix B, eXtensible Markup Language (XML) Document Type Definition for Dublin Core Simple.

The Dublin Core Element Set (http://dublincore.org/documents/dces) is widely recognized as a means of achieving semantic interoperability between resource descriptions from a variety of domains. Used in conjunction with Z39.50, the fifteen Dublin Core elements are currently represented as bib-1 Use attributes.

Functional Area C utilizes the following Z39.50 Objects:

** Z-servers will support one of either SUTRS or XML

Record Syntax "support" means that the Z-server can deliver any record in a result set formatted in a required record syntax and a Z-client can receive and process for display or other uses any record formatted in a required record syntax. Exceptional server situations may override this required syntax requirement (e.g., database temporarily not available). Local policies may also restrict access to records in one or more specific record syntaxes to authorized users. In such cases, the server should return the appropriate diagnostic. Servers that provide records in selected record syntaxes for specific authorized users should use bib-1 Diagnostic #1070: "User not authorized to receive this record in requested syntax."

This profile does not attempt to specify the data elements or indexes to be mapped to the required bib-1 Use attributes. It recognizes that indexing practices may vary based on local metadata sets and needs. However, implementors that have already mapped their local metadata sets (including MARC) to Dublin Core (DC) Simple elements should base their Use Attributes on the following equivalencies:

• A creator search will look for matches in the DC creator element
• A title search will look for matches in the DC title element
• A subject search will look for matches in the DC subject element
• An identifier search will look for matches in the DC identifier element
• A date of publication search will look for matches in the DC date element
• An "any" search will search commonly used access points defined by the server; since Level 0 and Level 1 specify searches for author, title, and subject, an "any" search should look for matches in the indexes related to those access points.

5.C.0. Functional Area C: Level 0 Cross-Domain Search and Retrieval

Level 0 Search enables basic cross-domain searching on Creator, Title, and Subject.

Version 2 is required, Version 3 is recommended.

Level 0 Retrieval requires:

• Z-clients to support SUTRS and XML
• Z-servers to support SUTRS or XML

Level 0 Searching requires support of the following bib-1 Attributes Types and Values:

Attribute Type	Attribute Values	Attribute Names
Use (1)	4, 21, 1003, 1016	title, subject heading, author, any
Relation (2)	3	equal
Position (3)	3	any position in field
Structure (4)	2	Word
Truncation (5)	100	Do not truncate
Completeness (6)	1	Incomplete subfield

The Bath Profile uses the Bib-1 Attribute Set when specifying searches; however, information retrieval systems work with indexes and access points. Throughout this section, where the terms field and/or subfield are used in Attribute Names (e.g., Incomplete Subfield), the term should be interpreted to mean access point.

Combinations of these Attributes Types and Values express the semantics of four Level 0 Searches detailed below:

• Creator Search -- Keyword
• Title Search -- Keyword
• Subject Search -- Keyword
• Any Search -- Keyword.

These four searches use the same attribute combinations as the searches defined in Section 5.A.0. Functional Area A: Level 0 Basic Search and Retrieval, however, the names and uses of the searches reflect a more generic approach (i.e., not oriented to library data) and semantics related to the Dublin Core Element Set.

5.C.0.1. Creator Search -- Keyword

Uses: Searches for complete word in data elements that contain names of entities primarily responsible for making the content of the resource; examples of a Creator include a person, an organisation, or a service.

Attribute Type	Attribute Values	Attribute Names
Use (1)	1003	author
Relation (2)	3	equal
Position (3)	3	any position in field
Structure (4)	2	Word
Truncation (5)	100	Do not truncate
Completeness (6)	1	Incomplete subfield

5.C.0.2. Title Search -- Keyword

Uses: Searches for complete word in data elements that contain the name given to a resource; typically, a Title will be a name by which the resource is formally known.

Attribute Type	Attribute Values	Attribute Names
Use (1)	4	title
Relation (2)	3	equal
Position (3)	3	any position in field
Structure (4)	2	Word
Truncation (5)	100	Do not truncate
Completeness (6)	1	Incomplete subfield

5.C.0.3. Subject Search -- Keyword

Uses: Searches for complete word in data elements that contain the topic of the conte of the resource; typically, a Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource.

Attribute Type	Attribute Values	Attribute Names
Use (1)	21	subject heading
Relation (2)	3	equal
Position (3)	3	any position in field
Structure (4)	2	Word
Truncation (5)	100	Do not truncate
Completeness (6)	1	Incomplete subfield

5.C.0.4. Any Search -- Keyword

Uses: Searches for complete word in data elements that are commonly used as access points (as defined by the server). Any searches comprising more than one keyword are interpreted in such a way that the terms may exist in the same or different attributes.

Example: a search on "Dickens AND Twist" might conceivably find "Dickens" in the Author Use Attribute (1003) and "Twist" in the Title Use Attribute (4).

Attribute Type	Attribute Values	Attribute Names
Use (1)	1016	any
Relation (2)	3	equal
Position (3)	3	any position in field
Structure (4)	2	Word
Truncation (5)	100	Do not truncate
Completeness (6)	1	Incomplete subfield