Work Package 8 - Functional Specification

BIBLINK

BIBLINK Workspace - Usage Scenario 1

In this scenario we consider a small Internet publisher, Publisher-X, who wish 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 the 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 mapping tables to allow the minimal BIBLINK UNIMARC record to be mapped to and from NatMARC records.

Here is a brief description of the flow of metadata between Publisher-X and the NBA using the BIBLINK Workspace (BW).

At various points in the flow, BW Events occur. An Event may be a record being created, a field in a BWR being updated or something else. Associated with each Event is an Action. An Action may be to send a particular view of a BWR somewhere, to update a field in a BWR based on one or more other fields in a BWR or something else. Events and their associated Actions are listed in the description below. The names of Events are provided as examples only.

  1. Publisher-X makes the Web pages for a new publication available on their Web server in the normal way.
  2. The publisher uses the BW Web form to create a new BIBLINK Workspace Record (BWR). This new record can be as simple or as complex as required (using the 18 elements in the BIBLINK Core (BC)) but must contain all the elements that the NBA have configured as mandatory in the BW (typically 'Title' and 'Identifier').
  3. The BW converts the BC into a partial UNIMARC record and stores it into the UNIMARC field in the new BWR.
    Event: RECORD-CREATED-by-Publisher-X. BC-UPDATED-by-Publisher-X.
    Action: Convert BC to UNIMARC
  4. The BW converts the partial UNIMARC record into a partial NatMARC record, and stores it into the NatMARC field in the BWR.
    Event: UNIMARC-UPDATED
    Action: Convert UNIMARC to NatMARC
  5. The BW sends an email message to the NBA containing a text copy of the BC and the partial NatMARC record.
    Event: NatMARC-UPDATED-from-UNIMARC
    Action: Send BC as text and NatMARC to NBA
  6. The NBA loads the NatMARC record into their local MARC based database and enhace it, viewing the Publisher's Web pages if necessary.
  7. The NBA uses email to send the enhanced version of the NatMARC record back to the BW.
  8. The BW stores the enhanced NatMARC record into the NatMARC field of the BWR.
  9. The BW converts the enhanced NatMARC record into an enhanced UNIMARC record using the minimal mapping supllied by the NBA.
    Event: NatMARC-UPDATED-by-NBA
    Action: Convert NatMARC to UNIMARC
  10. The BW updates some or all of the BC fields based on the enhanced UNIMARC record.
    Event: UNIMARC-UPDATED-from-NatMARC
    Action: Convert UNIMARC to BC
  11. The BW sends an email message to Publisher-X containing an HTML (META tag) version of the enhanced BC fields.
    Event: BC-UPDATED-from-UNIMARC
    Action: Send BC as HTML to Publisher-X
  12. The NBA sends an email message to the BW indicating that the BWR is now complete. (Note that it may well be possible to combine this with step 7 above).
  13. The BW locks the BWR so that no further updates can be made to it.
    Event: RECORD-COMPLETE
    Action: Lock record
  14. Publisher-X copies the HTML META tags from the email message and embeds them into the HEAD section of the publication's home page.
Maintained by: Andy Powell
Last modified: