Trudi Noordermeer describes BIBLINK (Linking Publishers and National Bibliographic Services) - a project to create a bibliographic link between publishers of electronic resources and national bibliographic agencies.
Project BIBLINK [1] aims to establish a relationship between national bibliographic agencies and publishers of electronic resources, in order to create authoritative bibliographic information that will benefit both sectors. In the digital information environment, the role of national bibliographic agencies will probably become increasingly dependent upon the generation of electronic links between publishers and other agents in the bibliographic chain. The concept of BIBLINK crystallised from the work of the EU concerted action CoBRA. It was recognised that the significant growth in electronic publishing could result in valuable publications being unrecorded as they would by-pass established national bibliographic procedures. Given the nature of the medium it was felt the issues could be most effectively addressed at an international level. Project BIBLINK takes advantage of the bibliographic expertise of five national libraries in Europe, working in conjunction with partners in the publishing sector and higher education, to examine the way in which electronic publications are described for catalogues and other listings and how this information can be transmitted between the two sectors.
BIBLINK is a proof of concept project to assess the feasibility of the direct exchange of data between publishers and national libraries. The overall objective of the project is to produce a demonstration system that will further the improvement of national bibliographic services by establishing a link between the publishers of electronic documents and national bibliographic agencies. This link will allow publishers of various types to transmit bibliographic data about electronic publications to their national bibliographic agency for inclusion in the bibliography. It will also allow for the resulting record to be re-transmittted to the publisher for embedding in the publication if so desired, or for use in other applications, such as sales promotions. These objectives can be detailed as follows:
The project officially started on 15 May 1996 and was divided into two phases, each of eighteen months duration. An extension was needed to the second phase in order to develop the system and to have time to run a meaningful demonstration phase. The end date of the project is now 15 February 2000. The first stage can be described as the research and consensus building phase during which information was gathered and analysed about the various components that contribute to a data generation, transmission and conversion system. The research entailed considerable discussion with publishers and consensus with them as to the most promising technical solutions to implement.
The following decisions were taken and the reports with detailed information are available via the BIBLINK website. The scope of the project is very broad: both on line and off line publications are taken into consideration. Several metadata formats were investigated and it was decided – in 1997! - to add three fields to the Dublin Core metadata set: the BIBLINK core metadata set (see Table 1). Several unique identifiers can be used like ISBN, ISSN, SICI and DOI. During consensus building workshops with the publishers decisions were taken about cooperation. The UNIMARC format was chosen as the central format and conversion is possible to and from several national MARC formats and to BIBLINK Core. For the conversion the USEMARCON software is used. For transmission of data email or a web form can be used. For authentication of publications and corresponding metadata a hash value is calculated. These were the results of the first phase.
In the second stage the demonstration system is being developed and tested and will be implemented. The company Jouve in Paris developed the software together with the project partners. The work began by formalising the User Requirements and producing a detailed Functional Specification and resulted in the demonstration and validation of a prototype system at various test sites. An exploitation plan is being developed to provide a framework for library partners to assess the possibility of incorporating the system in operational procedures.
| BIBLINK data element | Brief description |
| DC.Title | Title of work |
| DC.Creator | Persons or organisations primary responsible for intellectual content |
| DC | Subject Subject keywords, may also contain terms from published subject headings or classification schemes |
| DC.Description | Description of content or abstract |
| DC.Publisher | Agency responsible for producing the publication |
| DC.Contributor | Persons or organisations responsible for content not included under DC.Creator |
| DC.Date | Date of publication |
| DC.Format | Format information |
| DC.Identifier | A unique identifier, e.g. ISBN, SICI or DOI |
| DC.Language | Language of text |
| DC.Rights | Terms and conditions information |
| BIBLINK.Checksum | Hash value or checksum computed for authentication purposes |
| BIBLINK.edition | Number of edition or version |
| BIBLINK.extent | The size of an item – number of files, bytes etc. |
| BIBLINK.Frequency | Frequency of issue if a serial publication |
| BIBLINK.PlacePublication | Geographical location of publisher |
| BIBLINK.Price | Price |
| BIBLINK.Systems | Requirements System Requirements |
Figure 1 shows a model of the BIBLINK Workspace. This is described in more detail in the following section.
 Figure 1: Model of the BIBLINK Workspace |
The core of the BIBLINK demonstrator consists of a computer mediated working environment called the BIBLINK Workspace (BW). It can be envisaged as a virtual workspace encompassing a database and functionality that allows, in the first instance, publishers to create records and subsequently give access to participants to retrieve, update and, ultimately, delete those records. The BW converts the data between the formats required by the various parties and provides the mechanisms necessary for the functioning and management of the system. It allows the various parties to view and download the records or elements in the records in different formats at various stages in the development of the record. Users are working in the BW according to a pre-established user profile defining access rights and those aspects of interaction with the BW that are configurable. The NBAs vary in the way they apply the use of the BW to their current procedures and each specified the flow of work within their own organisation. They wanted to configure the actions that the BW carries out in relation to events in the life of the BIBLINK Workspace Records (BWR) according to local practices. For example one NBA may want to be notified about a new record as soon as it is created by a publisher, whereas another will only want to be notified once a specified third party like an ISBN office has added an identifier to a new record. The situation is similar with the publisher participants: one wants to be sent an enhanced BC record as soon as the NBA has updated the original but another wishes only to be notified that an identifier has been added to allow them to retrieve it when they are ready to do so. These preferences are specified in the User Profile established for each participant. To give a picture of how the flow of metadata from publisher to NBA and back is envisaged, an examples of usage scenario is given below.
In this scenario we consider a small Internet publisher Publisher-X, who wishes to supply simple metadata about their publications to the National Bibliographic Agency (NBA) in order that each publication appears in the National Bibliography and so that an enhanced Dublin Core-like bibliographic record can be embedded into the HTML of Publisher-X's Web pages. Publications are made available on the Web prior to notification being sent to the NBA. No formal 'identifier', such as an ISSN or DOI, is required for each publication. The NBA in question has provided a set of conversion tables to allow the minimal BIBLINK UNIMARC record to be converted to and from NatMARC records. Below is a brief description of the flow of metadata between Publisher-X and the NBA using the BIBLINK Workspace (BW).
Other scenarios are also available [2].
At the time of writing (December 1999) the BIBLINK partners are working on the demonstration. In February 2000 approximately 2000 bibliographic records of electronic resources, 400 of each national library, will be available in the BIBLINK Workspace. The national libraries are working on the implementation of BIBLINK in the existing workflow of their national bibliographic agencies. The software is available for UNIX and Windows.
Trudi Noordermeer
Koninklijke Bibliotheek
National Library of the Netherlands
Senior Researcher
Department of Research and Network Information
PO Box 90407
2509 LK Den Haag
The Netherlands
Tel : + 31-70-3140597
Fax : + 31-70-3140424
Email : trudi.noordermeer@konbib.nl
KB website at <http://www.konbib.nl/>
BIBLINK website at <http://hosted.ukoln.ac.uk/biblink/>
For citation purposes:
Noordermeer, T.,"A Bibliographic Link Between Publishers Of Electronic Resources And National Bibliographic Agencies: Project BIBLINK", Exploit Interactive issue 4, January 2000
<URL: http://www.exploit-lib.org/issue4/biblink/>
[HTML Validation] - [Accessibility check]
|
Issue Home | Editorial | Features | Regular Columns | News and Events | Et cetera | ||
|
| ||
| Go to Top |
A UKOLN Service. Contact Us. Copyright © 1999 |
Last Updated: 10 January 2000 |