Work Package 8

BIBLINK Core Field Semantics

The BIBLINK Project

This page lists the semantics of the 19 BIBLINK Core fields and gives some examples of their intended use. Many of the field definitions are based on the equivalent Dublin Core element definitions:

<URL:http://purl.org/metadata/dublin_core_elements>

Semantics

BC Field Semantics Examples

BIBLINK.Checksum

An MD5 message digest (checksum) generated from the resource. (The algorithm for calculating the MD5 message digest is described elsewhere).

fd66e37fb693491e84e184b092121265

BIBLINK.Edition

A text string indicating the version or edition of the resource.

2nd Ed.

BIBLINK.Extent

The 'size' of the resource - in bytes, number of files or number of CD-ROMs for example.

2 computer laser optical disks; 4 3/4 in

BIBLINK.Frequency

The frequency of issue if a serial publication.

Monthly
Six times per year

BIBLINK.PlacePublication

Geographic location of publisher.

Manchester

BIBLINK.Price

A simple, retail price. More complex licensing information should be provided using the DC.Rights field.

£3.99
FF50.00

BIBLINK.SystemRequirements

Hardware or software requirements for the system needed to view the resource.

Multimedia PC 486x or higher, 8mb memory, CD-ROM drive, sound card, SVGA 256-colour monitor, Windows 95 or Windows 3.1
Microsoft Internet Explorer 4.0

DC.Creator

The person primarily responsible for creating the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources.

Jacques Paul Migne

DC.Creator.Organization

The name of an institution or corporation primarily responsible for creating the intellectual content of the resource.

Cambridge University Library

DC.Contributor

A person not specified in the DC.Creator field who has made significant intellectual contributions to the resource but whose contribution is secondary to any person or organisation specified in the DC.Creator field (for example an editor, transcriber, or illustrator).

Paul Miller

DC.Contributor.Organization

An institution or corporation that has made significant intellectual contributions to the resource but whose contribution is secondary to any person or organisation specified in the DC.Creator and DC.Creator.Organization fields.

Arts and Humanities Data Service

DC.Date

A date associated with the creation or availability of the resource. The date format should conform to ISO 8601 that includes (among others) dates of the forms YYYY and YYYY-MM-DD.

1998

DC.Description

A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources.

A Web and print magazine of Internet issues for librarians and information specialists

DC.Format

The data format of the resource. Where possible this should be given as a MIME type.

application/pdf
text/html

DC.Identifier

A string or number used to uniquely identify the resource. A URI, DOI, ISBN, ISSN or SICI.

http://www.ariadne.ac.uk/
0-89887-113-1

DC.Language

The language of the intellectual content of the resource. Where practical, the content of this field should coincide with RFC 1766; examples include en, de, es, fi, fr, ja, th, and zh.

en

DC.Publisher

The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity.

British Council

DC.Rights

A rights management statement, an identifier that links to a rights management statement, or an identifier that links to a service providing information about rights management for the resource.

http://www-uk.gnu.org/copyleft/gpl.html
http://www.pro.gov.uk/about/disclaimer.htm
DC.Source Information about a second resource from which the present resource is derived.
DC.Subject The topic of the resource. Typically, subject will be expressed as keywords or phrases that describe the subject or content of the resource. Alternatively, an LCSH, DDC, UDC, LCC subject heading may be used. Christian literature, Early -- Latin authors - Texts
Taylor-Schechter Genizah Research Unit; Cairo Geniza, papyrus
DC.Title

The main title or name given to the resource, usually by the creator or publisher.

Archives Direct 2001 Programme
Taylor-Schechter Unit Home Page
Patrologia Latina Database

DC.Title.Alternate

A title other than the main title; including subtitle, translated title, series title, vernacular name, etc.

AD2001 Programme
Plans for the Online Public Record Office

Issues

1. Does the BIBLINK Core need a Source field?

A field to record the "source" would be useful i.e. that the publication was an electronic version of a paper original. The BIBLINK core set doesn't include the original DC source element. Can we accomodate it now? Could it fit into the BC "Edition" element?

2. Should PlacePublication contain the country as well as the city?

BIBLINK PlacePublication - should this have the country as well?

Examples

The following examples are shown using HTML 4.0 <META> tags:

<META NAME="BIBLINK.Checksum" CONTENT="fd66e37fb693491e84e184b092121265">

<META NAME="BIBLINK.Edition" CONTENT="2nd Ed.">

<META NAME="BIBLINK.Extent" CONTENT="2 computer laser optical disks; 4 3/4 in">

<META NAME="BIBLINK.Frequency" CONTENT="Monthly">
<META NAME="BIBLINK.Frequency" CONTENT="Six times per year">

<META NAME="BIBLINK.PlacePublication" CONTENT="Manchester">

<META NAME="BIBLINK.Price" CONTENT="&#163;3.99">
<META NAME="BIBLINK.Price" CONTENT="FF50.00">

<META NAME="BIBLINK.SystemRequirements" CONTENT="Multimedia PC 486x or higher, 8mb memory, CD-ROM drive, sound card, SVGA 256-colour monitor, Windows 95 or Windows 3.1">
<META NAME="BIBLINK.SystemRequirements" CONTENT="Microsoft Internet Explorer 4.0">


Maintained by: Andy Powell
Last updated: 28-July-1998