SPEC Kit 325: Digital Preservation · 83
Columbia University
Columbia’s Long-Term Digital Preservation Archive (LTA). Status Report
http://www.columbia.edu/cu/libraries/inside/projects/digital_pres/lta/plan_current.html
CUL/IS Long Term Digital Preservation
http://www.columbia.edu/cu/libraries/inside/projects/digital_pres/lta/plan_current.html[10/5/11 12:18:49 PM]
a “leader/follower” configuration, to provide replication and failover support.
3. Application and Authentication Middleware
CUL/IS has configured middleware to support common application needs, including but not limited to
search and authentication/authorization. Authentication and authorization are built leveraging the
University’s identity management system that is based on Kerberos, LDAP and Shibboleth.
4. Long-Term Digital Archive Content and Applications
In 2009 we began loading content into our long-term digital preservation archive on the Fedora
platform. As part of this ingest process, descriptive, structural and rights metadata will be
reformulated according to current standards (e.g. MODS, METS, PREMIS, AES), and technical metadata
will be generated automatically (e.g., using JHOVE) when feasible. New institutional policies and
procedures required for meeting the standard of a “trusted digital repository” will be substantially
complete by July 2011. The digital preservation repository will also be functionally integrated with our
evolving digital asset management system, so that digital content of all kinds can be repurposed and
for use by both the Columbia community as well as external users.
At present the range of content we will be preserving in our LTA include: digitized library collections
(largely special and rare materials), content input into our local institutional repository (Academic
Commons) and, on a test basis, web sites harvested as part of a grant-funded pilot program.
In implementing our local applications and policies supporting the LTA, we will be guided by the May
2002 report "Trusted Digital Repositories, Attributes and Responsibilities: An RLG-OCLC
Report" along with other more recent research and best practices.
References
NYSERNet Data Center: http://www.nysernet.org/services/bcc/
Iron Mountain: http://www.ironmountain.com/dataprotection/vault/
Sun StorageTek SAM Software:
http://www.sun.com/storagetek/management_software/data_management/sam/
Columbia Libraries Digital Program
Last revision: 10/28/10
© Columbia University Libraries
Columbia University
Columbia’s Long-Term Digital Preservation Archive (LTA). Status Report
http://www.columbia.edu/cu/libraries/inside/projects/digital_pres/lta/plan_current.html
CUL/IS Long Term Digital Preservation
http://www.columbia.edu/cu/libraries/inside/projects/digital_pres/lta/plan_current.html[10/5/11 12:18:49 PM]
a “leader/follower” configuration, to provide replication and failover support.
3. Application and Authentication Middleware
CUL/IS has configured middleware to support common application needs, including but not limited to
search and authentication/authorization. Authentication and authorization are built leveraging the
University’s identity management system that is based on Kerberos, LDAP and Shibboleth.
4. Long-Term Digital Archive Content and Applications
In 2009 we began loading content into our long-term digital preservation archive on the Fedora
platform. As part of this ingest process, descriptive, structural and rights metadata will be
reformulated according to current standards (e.g. MODS, METS, PREMIS, AES), and technical metadata
will be generated automatically (e.g., using JHOVE) when feasible. New institutional policies and
procedures required for meeting the standard of a “trusted digital repository” will be substantially
complete by July 2011. The digital preservation repository will also be functionally integrated with our
evolving digital asset management system, so that digital content of all kinds can be repurposed and
for use by both the Columbia community as well as external users.
At present the range of content we will be preserving in our LTA include: digitized library collections
(largely special and rare materials), content input into our local institutional repository (Academic
Commons) and, on a test basis, web sites harvested as part of a grant-funded pilot program.
In implementing our local applications and policies supporting the LTA, we will be guided by the May
2002 report "Trusted Digital Repositories, Attributes and Responsibilities: An RLG-OCLC
Report" along with other more recent research and best practices.
References
NYSERNet Data Center: http://www.nysernet.org/services/bcc/
Iron Mountain: http://www.ironmountain.com/dataprotection/vault/
Sun StorageTek SAM Software:
http://www.sun.com/storagetek/management_software/data_management/sam/
Columbia Libraries Digital Program
Last revision: 10/28/10
© Columbia University Libraries
