Introducing UCLA’s ERDb(Electronic Resources Database)

Anita ColbyUCLA Science & Engineering Library

Development Principles

We needed a system that would• Capture all of the data needed to manage individual

licensed resources, packages and their components, and free resources throughout the lifecycle of the resources

• Migrate data or link out to data whenever possible to minimize the amount of redundant data entry.

• Track access problems and use• Facilitate communication about resources and record the

outcomes of key steps in the workflow in a non-uniform decentralized work environment

• Enhance subject access to e-resources by patrons and enable librarians to generate web pages dynamically.

Staff ERDb is searchable by

• Access provider• Catalog control number• ISSN• Keyword(s)• Language• OCLC number• Publisher• Resource ID number• Title ID number• Title phrase• Title words• Vendor

Staff ERDb is also searchable and limitable by

• 1 of 80 broad subject terms that largely reflect departmental divisions (e.g., anthropology, civil engineering). Subject terms are mapped to LC classification of resource

• 1 of 98 resource types (i.e, e-journals, dictionaries)

The client is segmented into a possible five screens

• Title

• Resource

• URL

• Status

• License

Title Screen(stores bibliographic and discovery metadata)

Resource Screen(stores selection and acquisitions information)

Status Screen(Permits the description and tracking of problems

and their resolution)

Status screen(also contains public messages regarding access)

URL screen(Lists active URLs for resources and data specific to each URL)

Licensing Screen (records licensing information and provisions)

Email Functionality