Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Table of Contents
maxLevel2
minLevel2
include.*:
stylenumber

...

Edit the

...

Edit the Record:

Check and edit the normal book parts of the record. Pay particular attention to name and subject headings. As far as possible the record should match any print records on Alma, and it is often easier to copy elements from the print record and paste them directly into the ebook record. Conversely it might sometimes be necessary to upgrade the print record at the same time.

It is not always possible to check all the details of an ebook record in the same way as a print record when the book is in front of you. You will need to make a judgement of the record based on its source, how complete it looks, and how it compares to the UCL print record. In general, trust the record if it seems to have come from a reputable source but you should be able to check the ebook directly and acessing it.

Delete any existing 533 or 590 field.

Apply a Template:

Each package needs to have specific data added to the record from a prepared template (see Creating a Template). To apply a template in the Alma Metadata Editor, select Edit>Expand from Template then choose the appropriate template from the list.

This will insert the following data:

  • 533 field (Electronic Reproduction Note)
  • 590 field (Access Note)
  • 590 field (Collection Tags)

You might then need to edit data, such as date of cataloguing.

Convert to Ebook Record:

Add more general ebook data to the record by using an Alma Normalization Rule. To do this in the Alma Metadata Editor, select Edit>Enhance the Record and choose the "Add Ebook Fields" Normalization Type from the list. This should do the following (although this might be changed over time):

  • Change LDR position 18 to "i"
  • Add 006 and 007 fields
  • Change 008 position 23 to "s"
  • Change all 020$$z to 020$$a
  • Update or create the 040 field, so that:
    • $$a is UkLUC for a new record
    • $$b is eng
    • $$e is rda
    • $$c is UkLUC for a new record
    • $$d is UkLUC for an amended record
  • Convert 300, so that:
    • Pagination is prefixed by "1 online resource" with pagination in brackets
    • $$c is deleted
  • Retain existing 336 fields but create a new one specifying text if there isn't one
  • Replace 337 and 338 with those appropriate to ebooks, or create new ones, as follows:
    • 337__$$a computer $$b c $$c rdamedia
    • 338__$$a online resource $$b cr $$c rdacarrier
  • Add a skeleton 533 field if this there isn't already one. This will need further editing.
  • Add a skeleton 590 field for access if there isn't already one. This will need checking if it is not the standard UCL one.
  • Add a skeleton 590 field for the package or collection tag.
  • Add a skeleton 590 for the date of editing.
  • Delete various unwanted fields, currently the following, although the list can easily be added to:

...

If the 533 and 590 fields were created by the Normalization Rule conversion, check and edit them.

Final Check and Save:

Perform a final quick check of the record, especially to make sure that none of the automatic edits from the Template and Normalization have not done anything unexpected. Email t.meehan@ucl.ac.uk if they have done something obviously wrong.

Creating a Template

533 field (Electronic Reproduction Note)

This says that this record is in fact an ebook and gives details about the ebook's publisher. See Creating a Template.

533__$$aElectronic reproduction. $$b <Place of publication> : $$c <Publisher>, $$d<date of publication>. $$n Available in <format> format. $$n Description based on contents viewed <date of cataloguing>.

(MARC21 documentation)

590 field (Access Note)

This specifies what the reader will need to access the ebook. See Creating a Template. In the vast majority of cases, this will be:

590 \\$aUCL username and password required for access.

(MARC21 documentation)

590 field (Collection Tags)

Tags are unique to a package or collection and enable us to identify, count, and delete collections. They all start "uclebk" and have a unique suffix, such as the following for the Hart collection. See Creating a Template.

590__$$a uclebkhart

fdfdfd