Work Package 8 - Functional Specification

BIBLINK

BIBLINK Workspace - Usage Scenario 2

In this scenario we consider a medium sized Internet publisher, Publisher-Y, who use SGML to prepare their publications and who wish to supply this to the National Bibliographic Agency (NBA) in order that each publication appears in the National Bibliography and so that an enhanced version of the SGML header can be obtained.

Publications are made available on the Web some time after notification has been sent to the NBA. An ISSN 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-Y 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-Y is working on a new publication and has prepared a minimal SGML header to describe it.
  2. Publisher-Y sends a copy of the SGML header to the BW using email.
  3. The BW creates a new BWR and stores the SGML header in the SGML-1 field.
  4. The BW converts SGML-1 into as many BC fields as necessary.
    Event: RECORD-CREATED-by-Publisher-Y, SGML-1-UPDATED-by-Publisher-Y
    Action: Convert SGML-1 to BC
  5. The BW converts the BC into a partial UNIMARC record and stores it into the UNIMARC field in the new BWR.
    Event: BC-UPDATED
    Action: Convert BC to UNIMARC
  6. 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
  7. The BW sends an email message to the ISSN Agency containing a text copy of the BC.
    Event: NatMARC-UPDATED-from-UNIMARC
    Action: Send BC as text to ISSN Agency
  8. The ISSN Agency assigns a new ISSN to the publication and sends an email message back to the BW to update the BC Identifier field (note this will actually cause the addition of a second BC Idenitifer field). The BC Identifier field is the only field in the BWR that the ISSN has been given access to modify.
  9. The BW converts the BC into a partial UNIMARC record and stores it into the UNIMARC field in the new BWR. It also flags the existing SGML-1 record as being out of date.
    Event: BC-UPDATED
    Action: Convert BC to UNIMARC. Mark SGML-1 as out of date
  10. 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
  11. The BW sends an email message to the NBA containing a text version of the DC fields.
    Event: NatMARC-UPDATED-from-UNIMARC
    Action: Send DC as text to NBA
  12. The NBA notes the new record but doesn't proceed until the publication appears on the Web.
  13. When the new publication is made available on the Web the NBA uses the Web interface to the BW to retrieve the partial NatMARC record and SGML-1 header.
  14. The NBA loads the NatMARC record into the local MARC based database and uses the SGML-1 header and the Web publication to enhance the NatMARC record.
  15. The NBA uses the Web interface to the BW to upload the enhanced version of the NatMARC record back to the BW.
  16. The BW stores the enhanced NatMARC record into the NatMARC field of the BWR.
  17. 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
  18. 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
  19. The BW sends an email message to Publisher-Y containing a text version of the enhanced BC fields.
    Event: BC-UPDATED-from-UNIMARC
    Action: Send BC as text to Publisher-Y
  20. 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 15 above).
  21. The BW locks the BWR so that no further updates can be made to it.
    Event: RECORD-COMPLETE
    Action: Lock record
  22. Publisher-Y uses the text version of the enhanced BC fields to create an enhanced SGML header for internal use.
Maintained by: Andy Powell
Last modified: