In June of 2010, Nelson left Western State College for a new position as the Metadata and Systems Librarian at Colorado College.

Colorado College

Almost immediately after starting in 2010, Nelson's development work first began automating the MARC record manipulation for loading into CC's legacy ILS as well as work on a thesis submission web application.


FRBR, short for Functional Requirements for Bibliographic Records, is a resource-entity representation for bibliographic entities that most significant use is in RDA - Resource Description and Access - an effort to replace AACR2 cataloging rules.

FRBR-Group-1-entities-and-basic-relations by Jakob Voss - own creation. Licensed under GFDL via Wikimedia Commons -
Source: Voss at
FRBR in E-Library
As mentioned in the previous slide, the Western's E-Library used FRBR representations of electronic resources stored on Google App Engine's commercial datastore.
FRBR Experiments at Colorado College
Initially experimentation with using Redis as a bibliographic datastore began in 2011 with attempting to model FRBR entities in Redis using a key pattern to represent the core properties of a FRBR entity Code4Lib 2012 . This research tested the capabilities of Redis's key-value datastore server starting with FRBR, and later moving to other vocabularies like VRA Core and FRBRoo. This project is available at

Redis Logo

Redis is an open-source key-value NoSQL data-storage technology where unique keys are associated can be associated with different data structure values like strings, lists, sets, hashes, that enable fast access to data because Redis stores everything in a computer's memory.

$ cd redis-2.8.18/src
$ ./redis-server
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.18 (819b1ef2/1) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 6148
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |         
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           

[6148] 06 Dec 14:40:48.980 # Server started, Redis version 2.8.18
[6148] 06 Dec 14:40:48.980 * The server is now ready to accept connections on port 6379

$ cd redis-2.8.18/src
$ ./redis-cli>> SET book:1:title hello
OK> EXISTS book:1:title
(integer) 1> TYPE book:1:title
string> DEL book:1:title
(integer) 1> EXISTS book:1:title
(integer) 0> TYPE book:1:title




BIBFRAME, short for Bibliographic Framework, is a Library of Congress initiative to replace MARC 21 with a Linked Data vocabulary. BIBFRAME is made up four major classes, Works, Instances, Annotations, and Authorities.



"… a resource reflecting a conceptual essence of the cataloging resource."


"… a resource reflecting an individual, material embodiment of the Work."


"… a resource that enhances our knowledge about another resource when knowing, minimally, 'who' is doing the annotating is important.


"… a resource reflecting key authority concepts that have defined relationships reflected in the Work and Instance. "

BIBFRAME Graphic and Descriptions of major BIBFRAME classes taken from