ArtFrame, led by Columbia University, is an extension of BIBFRAME to describe art objects, both two-dimensional (e.g., paintings, photographs) and three-dimensional (e.g., sculptures, ceramics).

Columbia Project Proposal

  • Application profile for the linked data description of art objects
  • Representative selection of BIBFRAME descriptions of art objects
  • Evaluation and publication of project findings


  • Starting development of application profile for ArtFrame.
  • Finalizing measurements, condition/preservation, and provenance modeling (together with RareMat Extension)

Arden Alexander (Library of Congress, Prints & Photographs)
Penny Baker (Clark Art Institute)
Andrea Puccio (Clark Art Institute)
Amber Billey (Columbia/OSMC)
Roberto Ferrari (Columbia/Art Properties)
Paul Frank (Library of Congress)
Kate Harcourt (Columbia/OSMC)
Robert Rendall (Columbia/OSMC)
Margaret Smithglass (Columbia/Avery)
Melanie Wacker (Columbia/OSMC)

Members of ARLIS/NA Cataloging Advisory Committee:

Marie-Chantal L'Écuyer-Coelho (Bibliotheque et Archives nationales Québec)
John A. Mair (Pratt Institute)
Sherman Clarke (freelance art cataloger)
Bronwen Bitetti (Bard College)
Tamara Fultz (Metropolitan Museum of Art)
Maria Oldal (Morgan Library & Museum)
Karen Stafford (Art Institute of Chicago)
Samantha Deutch (Frick Collection)

Link to working documents (for partners only)

Last updated 03/31/2017

Months 11-12 (February-March 2017)

Month 9- 10 (December 2016-January 2017)

Month 8 (November 2016) 

 Months 5-7 (August-October 2016)

  • Continue use case development

  • Group related use cases

  • Prioritize use cases

  • Develop ontology requirements based on use cases

  • Contribute MARCXML test records for LD4L MARC to BIBFRAME converter development

  Month 4 (July 2016) 

  • Create Art Extension Group that now includes members of the Library of Congress Prints and Photographs Division, the ARLIS/NA Cataloging Advisory Committee and Penny Baker from the Sterling and Francine Clark Art Institute. First call held July 6, 2016; followed by regular bi-weekly calls

  • Develop use cases (more than 30 by end of July)