CASE-1 NY Philharmonic Case Study


Published on

The NY Philharmonic is currently archiving their entire 200-year history, which includes historical documents, music scores, programs, marketing material and business records. The solution has currently ingested terabytes of data and the final archive will contain petabytes, all stored and managed by Alfresco. Ingestion process imports assets, all of which are compromised of multiple images that are taken with digital cameras. This session will articulate how systems such as OpenMigrate, Imagemagick and SOLR were used in the process. We’ll discuss how the content model is comprised of custom aspects, custom associations, and we keep the repository running quickly.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

CASE-1 NY Philharmonic Case Study

  1. 1. Digitizing the New YorkPhilharmonic ArchivesMitch Brodsky, Digital Archives Project ManagerAlfresco DevCon 2011@NYPhilArchive
  2. 2. About the New York Philharmonic •  Oldest Symphony Orchestra in the United States •  Began in 1842 •  Formed as a co-operative organization •  A “save everything” culture Alfresco Use Case - NYP Digital Archives Page 2
  3. 3. Project Scope 3,200 Programs 1,300 Marked Scores 72 Scrapbooks The International Era 1943-1970 8,000 Business Record Folders 8,500 Photographs 4,200 Glass Lantern Slides Alfresco Use Case - NYP Digital Archives Page 3
  4. 4. By the end of 2012 1.3 million pages 10 million nodes 15 Terabytes And we’re only getting started…Alfresco Use Case - NYP Digital Archives Page 4
  5. 5. Our Objectives •  Accurate representation of originals •  Comprehensive •  Easily/Freely Accessible •  A New, Sharable Model •  One repository: December 7, 1842 --> YESTERDAY DO MORE, SEE MORE, USE MORE, SHARE MORE GO
  6. 6. Alfresco Use Case - NYP Digital Archives Page 6
  7. 7. Public UserSoftware Architecture Web Front End APACHE SOLR Alfresco Use Case - NYP Digital Archives Page 7
  8. 8. Public User Software Architecture Web Front End Additional SOLR Metadata XML: layer: - Adds security Different content model per doctype - Adds control Creates content node for storing metadata - Relieves Dependencies and associationsImage capture Storage - Faceted Search OM creates nodes in pre-defined hierarchy Image Conversion - Other advanced capabilities Doctype APACHE SOLR Intermediate organization system (different per doctype) “pages” ID 1 Asset Asset ID 2 Page 001 “metadata” Page 002Content Item -  Properties populated with metadata -  Holds associations to images Source Metadata Alfresco Use Case - NYP Digital Archives Page 8
  9. 9. What We Want •  Data Entry •  Form Designer •  Metadata Templating •  Predefined Validation lists •  Improve Client Capacity •  Workflows or Document Library •  JPEG2000 (integration with Djatoka server) •  Completely isolate our SOLR-driven front end from Alf DB
  10. 10. Next Steps •  OCR •  Automate Workflows with Activiti •  Integrate Digital Preservation Tools •  Hook in Social Media apps
  11. 11. Visit Us Mitch Brodsky, Digital Archives Project Manager (212) 875-5933