Versions Compared

Key

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

Marmot uses Marcive authority service to maintain authorized headings in our databases.


Anchor
topofpage
topofpage
Table of Contents

Table of Contents

Database backfile

At the start of authority service with Marcive we sent them a copy of our entire database of MARC records. This is called the backfile.

New record processing

New records are sent to Marcive at the beginning of each month for each database. These new records are added to the backfile, so they have a complete copy of our databases.

When we send them new records, they send back copies of our records with any updates or changes they make to the records. These changes are loaded into our database.

Comprehensive Update

On a regular basis Marcive will send us records with updates to headings, such as changes to names or subject terms. Both MLN1 and MLN2 get a comprehensive updates quarterly.

Each database user group has made different decisions about what changes they want Marcive to make.

This is the processing profile document for MLN1

View file
nameMarmot Marcive Customer Profile.pdf

MLN1 Processing Details

This is the processing profile document for MLN2

View file
nameappr-cust_flir.pdf

MLN2 Processing Details

Marcive’s guide to processing details:

View file
nameappr-guide.pdf

Protected Fields for Marcive Bib Record Loading

MLN1 Protected Fields

MLN2 Protected Fields

Top of page

Warnings

This process means that Marcive will store a copy of your records. Periodically they will send copies of these records back and overlay the records in our databases with updates. If you have locally changed a record in the mean time, that information may be lost when the Marcive version of the record overlays the record in our database.

The way to avoid this is to send Marcive a new copy of a record if you update it locally. You can do this by updating the CAT DATE. Records with a new CAT DATE will be sent to Marcive again in the next monthly update. Then the new record will be what comes back with updates.

Log of authority actions

We keep a logs of all authority actions here:

https://docs.google.com/document/d/1jtd8gH1on88nF-3UEvPRSFPmQBO7rmJ2JoRKeFkdT8o/edit?usp=sharing

https://docs.google.com/document/d/1L-a5j2kSsUL25mT7pwLKQ6AniLNu3kv7dSmd-Fzsyb4/edit?usp=sharing

Top of page

Related Documentation

Page Properties
Filter by label (Content by label)
showLabelsfalse
cqllabel = "label"