Record Metadata Context Set

Introduction

This context set was created to address the need for record metadata searches as opposed to searches within the records themselves. It was constructed according to the rules of the ISO/IEC 11179 element naming standard.

All of the following indexes are assumed to be with reference to a single 'native' data format for the record, even if transformations are later requested. For example, if a query references the size of the record and asks for it to be returned in the Dublin Core record schema, then the size is not necessarily that of the DC representation.

The identifier for the Record Metadata context set is: info:srw/cql-context-set/2/rec-1.1
The recommended prefix for the Record Metadata context set is: rec
Definition of the index name components.

Indexes

Index NameDescription
Basic Information
identifierA unique local identifier for the record within the current context
versionIdentifierVersion information for the record
checksumValueChecksum string for the record
noteTextText of a note associated with the record
languageCodeCode for the language of the record
formatCodeThe format of the record (eg record schema, record syntax)
typeCodeA categorisation of the record (eg bibliographic vs authority)
byteCountThe bytes in the record (size)
wordCountThe number of words in the record
statusCodeA code recording the current status of the record (eg published, accepted, locked)
locationIdentiferThe location of a record (eg directory structure, SQL table, recordStore identifier)
resultsetPositionThe position of the record within a result set
relevanceValueThe computed relevance score for the record (see the relevance set)
relevancePositionThe position of the record in order of relevance, even if the resultSet has been otherwise sorted
collectionCountNumber of (known) collections which contain this record
collectionNameName of a collection which contains this record
collectionIdentifierIdentifier for a collection which contains this record
authorityIndicatorIs the record the authoritative source for the object that it describes, or might there be another record which is more authoritative
Events and History
creationDateDate/Time at which the record was created
creationAgentNameName of the agent responsible for creation of the record
modificationDateDate/Time at which the record was modified
modificationAgentNameName of an agent responsible for modifying the record
modificationTypeType of a modification made to the record
lastModificationDateDate/Time at which the record was last modified
lastModificationAgentNameName of the agent responsible for last modifying the record
lastModificationTypeType of the last modification made to the record
submissionDateDate/Time at which the record was submitted to the current context
submissionAgentNameName of the agent responsible for submitting the record
publicationDateDate/Time at which the record was published
publicationAgentNameName of the agent responsible for publishing the record
retrievalDateDate/Time at which the record was retrieved
retrievalAgentNameName of the agent which retrieved the record
lastRetrievalDateDate/Time at which the record was last retrieved
lastRetrievalAgentNameName of the agent which last retrieved the record
retrievalCountThe number of times the record has been retrieved

Relation Modifiers

Modifier NameDescription
checksumCodeA Code for the checksum algorithm to be used (eg MD5, SHA-0, SHA-1,etc)

Examples

  1. If your client is only able to display records under 50 kilobytes, you might have a query like:
    dc.title any fish and rec.byteCount < 51200
    to retrieve only files with a title that includes 'fish' and are less than the client's maximum size.
  2. If you wanted to find records that were have been recently updated by a user, you might send a query like:
    rec.lastModificationDate > "2002-12-05T18:00:00" and rec.lastModificationAgentName="azaroth"