DLF Wiki - User contributions [en]

NDSA:Columbia University

2011-06-08T20:27:26Z

Rtc:

#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#* Design & implement coherent & comprehensive preservation program for ensuring survival & continued accessibility of Libraries’ digital content. Develop & budget for long-term digital archiving strategy for content created by the Libraries, whether “born-digital” or converted from analog formats.
#* Provide stable, secure storage for large-scale access & long- term preservation
#* Support efficient creation & management of administrative, descriptive, structural, preservation & rights metadata
#* Support object relationships, actions, behaviors, fine-grained access control policies
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#* Fedora version 3
#* SUN SAM-FS platform, four copies, two on disk, two on tape
#* 70TB effective storage with 9.6TB tier I disk cache
#* Offsite disk storage at NYSERNet Data Center, Syracuse, New York, dedicated 1Gb/s network link to Columbia
#* Risk averse - use "tried and true" technologies
#* Open to maximize sustainability and flexibility
#* Entrance and exit strategy
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#* text, images, data sets, audio, limited video
#How big is your collection? (In terms of number of objects and storage space required)
#* TBD
#What are your performance requirements? Further, why are these your particular requirements?
#* System is an "accessible repository" with low latency access to data.
#* Decision to build consolidated system based on current size of collection, desire to provide ready access to materials.
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#* Two copies of disk, two copies on tape, with one remote disk copy in Syracuse.
#* Two copies on disk support fixity checking.
#* Tape copy supports offline and offsite backup.
#What do you think the key advantages of the system you use?
#* SAM automatically replicates data based on defined policies
#* SAM automatically brings data from SATA storage into higher performance fibre-channel storage
#What do you think are the key problems or disadvantages your system present?
#* System was a conservative choice, has commercial support, and has met our needs.
#* Oracle acquisition has created some uncertainty regarding hardware.
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
#* We will migrate at the end of the equipment lifecycle (4-5 years). We haven't decided if we will migrate off of SAM-FS.
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

NDSA:Columbia University

2011-06-08T20:24:01Z

Rtc:

#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#* Design & implement coherent & comprehensive preservation program for ensuring survival & continued accessibility of Libraries’ digital content. Develop & budget for long-term digital archiving strategy for content created by the Libraries, whether “born-digital” or converted from analog formats.
#* Provide stable, secure storage for large-scale access & long- term preservation
#* Support efficient creation & management of administrative, descriptive, structural, preservation & rights metadata
#* Support object relationships, actions, behaviors, fine-grained access control policies
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#* Fedora version 3
#* SUN SAM-FS platform, four copies, two on disk, two on tape
#* 70TB effective storage with 9.6TB tier I disk cache
#* Offsite disk storage at NYSERNet Data Center, Syracuse, New York, dedicated 1Gb/s network link to Columbia
#* Risk averse - use "tried and true" technologies
#* Open to maximize sustainability and flexibility
#* Entrance and exit strategy
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#* text, images, data sets, audio, limited video
#How big is your collection? (In terms of number of objects and storage space required)
#* TBD
#What are your performance requirements? Further, why are these your particular requirements?
#* System is an "accessible repository" with low latency access to data.
#* Decision to build consolidated system based on current size of collection, desire to provide ready access to materials.
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#* Two copies of disk, two copies on tape, with one remote disk copy in Syracuse.
#* Two copies on disk support fixity checking.
#* Tape copy supports offline and offsite backup.
#What do you think the key advantages of the system you use?
#* SAM automatically replicates data based on defined policies
#* SAM automatically brings data from SATA storage into higher performance fibre-channel storage
#*
#What do you think are the key problems or disadvantages your system present?
#*
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
#* NA
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

NDSA:Columbia University

2011-06-08T20:23:15Z

Rtc:

#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#* Design & implement coherent & comprehensive preservation program for ensuring survival & continued accessibility of Libraries’ digital content. Develop & budget for long-term digital archiving strategy for content created by the Libraries, whether “born-digital” or converted from analog formats.
#* Provide stable, secure storage for large-scale access & long- term preservation
#* Support efficient creation & management of administrative, descriptive, structural, preservation & rights metadata
#* Support object relationships, actions, behaviors, fine-grained access control policies
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#* Fedora version 3
#* SUN SAM-FS platform, four copies, two on disk, two on tape
#* 70TB effective storage with 9.6TB tier I disk cache
#* Offsite disk storage at NYSERNet Data Center, Syracuse, New York, dedicated 1Gb/s network link to Columbia
#* Risk averse - use "tried and true" technologies
#* Open to maximize sustainability and flexibility
#* Entrance and exit strategy
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#* text, images, data sets, audio, limited video
#How big is your collection? (In terms of number of objects and storage space required)
#* TBD
#What are your performance requirements? Further, why are these your particular requirements?
#* System is an "accessible repository" with low latency access to data.
#* Decision to build consolidated system based on current size of collection, desire to provide ready access to materials.
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#* Two copies of disk, two copies on tape, with one remote disk copy in Syracuse.
#* Two copies on disk support fixity checking.
#* Tape copy supports offline and offsite backup.
#What do you think the key advantages of the system you use?
#* SAM automatically replicates data based on defined policies
#* SAM automatically brings data from SATA storage into higher performance fibre-channel storage
#*

#What do you think are the key problems or disadvantages your system present?
#*
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

NDSA:Columbia University

2011-06-08T20:17:29Z

Rtc:

#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#* Design & implement coherent & comprehensive preservation program for ensuring survival & continued accessibility of Libraries’ digital content. Develop & budget for long-term digital archiving strategy for content created by the Libraries, whether “born-digital” or converted from analog formats.
#* Provide stable, secure storage for large-scale access & long- term preservation
#* Support efficient creation & management of administrative, descriptive, structural, preservation & rights metadata
#* Support object relationships, actions, behaviors, fine-grained access control policies
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#* SUN SAM-FS platform, four copies, two on disk, two on tape
#* 70TB effective storage with 9.6TB tier I disk cache
#* Offsite disk storage at NYSERNet Data Center, Syracuse, New York, dedicated 1Gb/s network link to Columbia
#* Risk averse - use "tried and true" technologies
#* Open to maximize sustainability and flexibility
#* Entrance and exit strategy
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#* text, images, data sets, audio, limited video
#How big is your collection? (In terms of number of objects and storage space required)
#*

#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

NDSA:Columbia University

2011-06-08T18:56:39Z

Rtc:

NDSA:Columbia University

2011-06-08T18:56:19Z

Rtc:

NDSA:Columbia University

2011-06-08T18:54:28Z

Rtc:

#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)

Design & implement coherent & comprehensive preservation program for ensuring survival & continued accessibility of Libraries’ digital content. Develop & budget for long-term digital archiving strategy for content created by the Libraries, whether “born-digital” or converted from analog formats.

#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

NDSA:Columbia University

2011-06-08T18:47:30Z

Rtc: Created page with ' #What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.) #What large scale stora…'

#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

NDSA:Cloud Presentations

2011-06-08T18:47:00Z

Rtc:

In each case we would want to identify who would present, who will contact them. Then when they will present.

From there we can include specific questions we would like them to respond to.

==Presentation Schedule and Slides==
# Feb 1, Tues, 1:00 EST call with iRods Reagan Moore ([[NDSA:Media:NIAID.ppt|presentation]])
# Feb 14, Monday, 11:00 EST call with Duracloud ([[NDSA:Media:DuracloudNDSA.ppt|presentation]])
# Feb 17, Thurs, 11:00 EST call with MetaArchive/GDDP Katherine Skinner, Matt Schultz and Martin Halbert MetaArchive NDSA ([[NDSA:Media:MetaArchive NDSA Infrastructure.ppt|presentation]])

==People/Projects to Contact==
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Questions for Cloud Service Presenters==
Here we are working on a set of general questions for presenters to develop talks around.

# What sort of use cases is your system designed to support? What doesn't this support?
# What preservation standards would your system support?
# What resources are required to support a solution implemented in your environment?
# What infrastructure do you rely on?
# How can your system impact digital preservation activities?
# If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
# What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice

===Responses to questions===
====[[NDSA:iRODS]] direct responses====

Other general notes:

* [Snavely] The need for each storage target to support a specific set of operations, and consistently with other storage targets, seems like a risk that comes along with the elegant abstraction that iRODS provides. Clear specifications help mitigate this risk.

====[[NDSA:DuraCloud]] direct responses====
Other general notes:

* [Snavely] Treatment of cloud provider is generally as a black box, without a strong sense of actual reliability of underlying storage systems. Cloud providers tend to promise checksum validation of contents, but recourse if validation fails was unknown (right?). Additional checksum validation has been augmented on top of cloud storage service by Duracloud.

====[[NDSA:MetaArchive/GDDP]] direct responses====
Other general notes:

* [Snavely] Built on LOCKSS, so data integrity assurances are provided by robust networked software model augmented to commodity hardware and storage. Federated nature provides integrity assurance but also a lack of central control in that the accidental loss of multiple caches is unlikely but e.g. scheduled maintenance or upgrades could coincidentally collide.

====Chronopolis====
# ...
====MicroSoft Azure====
# ...
====Amazon S3/EC2====
# ...

==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

===Responses to questions===

====[[NDSA:Florida Center for Library Automation]]====

====[[NDSA:Harvard Library]]====

====[[NDSA:HathiTrust]]====

====[[NDSA:National Library of Medicine Responses]]====

====[[NDSA:Penn State]]====

====[[NDSA:WGBH Responses]]====

====[[NDSA:NYU Response]]====

====[[NDSA:Library of Congress]]====

====[[NDSA:Columbia University]]====

====[[NDSA:Your Institution Here]]====

==General Concerns==
# confidential data
# encrypted data
# auditing
# preservation risks
# legal compliance
# ...

==Solution Models and Environments==
{| border="1"
!Name
!Offered as Service
!Deployed Locally
!Opensource
!Authentication Scheme
!Ingest Mechanism
!Export Mechanism
!Integrity/Validation Mechanism
!Replication Mechanism
!Administration Model (Federated, etc.)
!Tiering Support
|-
|iRODS
|
|
|
|
|
|
|
|
|
|
|-
|DuraCloud
|yes
|yes
|yes (Apache2)
|Basic Auth
|1:web-ui, 2:client-side utility, 3:REST-API
|1:web-ui, 2:client-side utility, 3:REST-API
|Checksum verified on ingest. On-demand checksum verification service.
|Built-in support for cross-cloud replication.
|
|
|-
|MetaArchive/GDDP
|
|
|
|
|
|
|
|
|
|
|-
|Chronopolis
|
|
|
|
|
|
|
|
|
|
|-
|Microsoft Azure
|
|
|
|
|
|
|
|
|
|
|-
|Amazon S3/EC2
|
|
|
|
|
|
|
|
|
|
|-
|}

NDSA:Cloud Presentations

2011-06-08T18:46:12Z

Rtc: Undo revision 1176 by Rtc (Talk)

In each case we would want to identify who would present, who will contact them. Then when they will present.

From there we can include specific questions we would like them to respond to.

==Presentation Schedule and Slides==
# Feb 1, Tues, 1:00 EST call with iRods Reagan Moore ([[NDSA:Media:NIAID.ppt|presentation]])
# Feb 14, Monday, 11:00 EST call with Duracloud ([[NDSA:Media:DuracloudNDSA.ppt|presentation]])
# Feb 17, Thurs, 11:00 EST call with MetaArchive/GDDP Katherine Skinner, Matt Schultz and Martin Halbert MetaArchive NDSA ([[NDSA:Media:MetaArchive NDSA Infrastructure.ppt|presentation]])

==People/Projects to Contact==
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Questions for Cloud Service Presenters==
Here we are working on a set of general questions for presenters to develop talks around.

# What sort of use cases is your system designed to support? What doesn't this support?
# What preservation standards would your system support?
# What resources are required to support a solution implemented in your environment?
# What infrastructure do you rely on?
# How can your system impact digital preservation activities?
# If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
# What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice

===Responses to questions===
====[[NDSA:iRODS]] direct responses====

Other general notes:

* [Snavely] The need for each storage target to support a specific set of operations, and consistently with other storage targets, seems like a risk that comes along with the elegant abstraction that iRODS provides. Clear specifications help mitigate this risk.

====[[NDSA:DuraCloud]] direct responses====
Other general notes:

* [Snavely] Treatment of cloud provider is generally as a black box, without a strong sense of actual reliability of underlying storage systems. Cloud providers tend to promise checksum validation of contents, but recourse if validation fails was unknown (right?). Additional checksum validation has been augmented on top of cloud storage service by Duracloud.

====[[NDSA:MetaArchive/GDDP]] direct responses====
Other general notes:

* [Snavely] Built on LOCKSS, so data integrity assurances are provided by robust networked software model augmented to commodity hardware and storage. Federated nature provides integrity assurance but also a lack of central control in that the accidental loss of multiple caches is unlikely but e.g. scheduled maintenance or upgrades could coincidentally collide.

====Chronopolis====
# ...
====MicroSoft Azure====
# ...
====Amazon S3/EC2====
# ...

==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

===Responses to questions===

====[[NDSA:Florida Center for Library Automation]]====

====[[NDSA:Harvard Library]]====

====[[NDSA:HathiTrust]]====

====[[NDSA:National Library of Medicine Responses]]====

====[[NDSA:Penn State]]====

====[[NDSA:WGBH Responses]]====

====[[NDSA:NYU Response]]====

====[[NDSA:Library of Congress]]====

====[[NDSA:Columbia University]]====

==General Concerns==
# confidential data
# encrypted data
# auditing
# preservation risks
# legal compliance
# ...

==Solution Models and Environments==
{| border="1"
!Name
!Offered as Service
!Deployed Locally
!Opensource
!Authentication Scheme
!Ingest Mechanism
!Export Mechanism
!Integrity/Validation Mechanism
!Replication Mechanism
!Administration Model (Federated, etc.)
!Tiering Support
|-
|iRODS
|
|
|
|
|
|
|
|
|
|
|-
|DuraCloud
|yes
|yes
|yes (Apache2)
|Basic Auth
|1:web-ui, 2:client-side utility, 3:REST-API
|1:web-ui, 2:client-side utility, 3:REST-API
|Checksum verified on ingest. On-demand checksum verification service.
|Built-in support for cross-cloud replication.
|
|
|-
|MetaArchive/GDDP
|
|
|
|
|
|
|
|
|
|
|-
|Chronopolis
|
|
|
|
|
|
|
|
|
|
|-
|Microsoft Azure
|
|
|
|
|
|
|
|
|
|
|-
|Amazon S3/EC2
|
|
|
|
|
|
|
|
|
|
|-
|}

NDSA:Cloud Presentations

2011-06-08T18:45:39Z

Rtc: Undo revision 1175 by Rtc (Talk)

In each case we would want to identify who would present, who will contact them. Then when they will present.

From there we can include specific questions we would like them to respond to.

==Presentation Schedule and Slides==
# Feb 1, Tues, 1:00 EST call with iRods Reagan Moore ([[NDSA:Media:NIAID.ppt|presentation]])
# Feb 14, Monday, 11:00 EST call with Duracloud ([[NDSA:Media:DuracloudNDSA.ppt|presentation]])
# Feb 17, Thurs, 11:00 EST call with MetaArchive/GDDP Katherine Skinner, Matt Schultz and Martin Halbert MetaArchive NDSA ([[NDSA:Media:MetaArchive NDSA Infrastructure.ppt|presentation]])

==People/Projects to Contact==
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Questions for Cloud Service Presenters==
Here we are working on a set of general questions for presenters to develop talks around.

# What sort of use cases is your system designed to support? What doesn't this support?
# What preservation standards would your system support?
# What resources are required to support a solution implemented in your environment?
# What infrastructure do you rely on?
# How can your system impact digital preservation activities?
# If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
# What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice

===Responses to questions===
====[[NDSA:iRODS]] direct responses====

Other general notes:

* [Snavely] The need for each storage target to support a specific set of operations, and consistently with other storage targets, seems like a risk that comes along with the elegant abstraction that iRODS provides. Clear specifications help mitigate this risk.

====[[NDSA:DuraCloud]] direct responses====
Other general notes:

* [Snavely] Treatment of cloud provider is generally as a black box, without a strong sense of actual reliability of underlying storage systems. Cloud providers tend to promise checksum validation of contents, but recourse if validation fails was unknown (right?). Additional checksum validation has been augmented on top of cloud storage service by Duracloud.

====[[NDSA:MetaArchive/GDDP]] direct responses====
Other general notes:

* [Snavely] Built on LOCKSS, so data integrity assurances are provided by robust networked software model augmented to commodity hardware and storage. Federated nature provides integrity assurance but also a lack of central control in that the accidental loss of multiple caches is unlikely but e.g. scheduled maintenance or upgrades could coincidentally collide.

====Chronopolis====
# ...
====MicroSoft Azure====
# ...
====Amazon S3/EC2====
# ...

==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

===Responses to questions===

====[[NDSA:Florida Center for Library Automation]]====

====[[NDSA:Harvard Library]]====

====[[NDSA:HathiTrust]]====

====[[NDSA:National Library of Medicine Responses]]====

====[[NDSA:Penn State]]====

====[[NDSA:WGBH Responses]]====

====[[NDSA:NYU Response]]====

====[[NDSA:Library of Congress]]====

====[[NDSA:Columbia University]]====

==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

====[[NDSA:Your Institution Here]]====

==General Concerns==
# confidential data
# encrypted data
# auditing
# preservation risks
# legal compliance
# ...

==Solution Models and Environments==
{| border="1"
!Name
!Offered as Service
!Deployed Locally
!Opensource
!Authentication Scheme
!Ingest Mechanism
!Export Mechanism
!Integrity/Validation Mechanism
!Replication Mechanism
!Administration Model (Federated, etc.)
!Tiering Support
|-
|iRODS
|
|
|
|
|
|
|
|
|
|
|-
|DuraCloud
|yes
|yes
|yes (Apache2)
|Basic Auth
|1:web-ui, 2:client-side utility, 3:REST-API
|1:web-ui, 2:client-side utility, 3:REST-API
|Checksum verified on ingest. On-demand checksum verification service.
|Built-in support for cross-cloud replication.
|
|
|-
|MetaArchive/GDDP
|
|
|
|
|
|
|
|
|
|
|-
|Chronopolis
|
|
|
|
|
|
|
|
|
|
|-
|Microsoft Azure
|
|
|
|
|
|
|
|
|
|
|-
|Amazon S3/EC2
|
|
|
|
|
|
|
|
|
|
|-
|}

NDSA:Cloud Presentations

2011-06-08T18:44:35Z

Rtc: /* Questions for Member Institution Implementations of Large Scale Storage Architectures */

In each case we would want to identify who would present, who will contact them. Then when they will present.

From there we can include specific questions we would like them to respond to.

==Presentation Schedule and Slides==
# Feb 1, Tues, 1:00 EST call with iRods Reagan Moore ([[NDSA:Media:NIAID.ppt|presentation]])
# Feb 14, Monday, 11:00 EST call with Duracloud ([[NDSA:Media:DuracloudNDSA.ppt|presentation]])
# Feb 17, Thurs, 11:00 EST call with MetaArchive/GDDP Katherine Skinner, Matt Schultz and Martin Halbert MetaArchive NDSA ([[NDSA:Media:MetaArchive NDSA Infrastructure.ppt|presentation]])

==People/Projects to Contact==
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Questions for Cloud Service Presenters==
Here we are working on a set of general questions for presenters to develop talks around.

# What sort of use cases is your system designed to support? What doesn't this support?
# What preservation standards would your system support?
# What resources are required to support a solution implemented in your environment?
# What infrastructure do you rely on?
# How can your system impact digital preservation activities?
# If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
# What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice

===Responses to questions===
====[[NDSA:iRODS]] direct responses====

Other general notes:

* [Snavely] The need for each storage target to support a specific set of operations, and consistently with other storage targets, seems like a risk that comes along with the elegant abstraction that iRODS provides. Clear specifications help mitigate this risk.

====[[NDSA:DuraCloud]] direct responses====
Other general notes:

* [Snavely] Treatment of cloud provider is generally as a black box, without a strong sense of actual reliability of underlying storage systems. Cloud providers tend to promise checksum validation of contents, but recourse if validation fails was unknown (right?). Additional checksum validation has been augmented on top of cloud storage service by Duracloud.

====[[NDSA:MetaArchive/GDDP]] direct responses====
Other general notes:

* [Snavely] Built on LOCKSS, so data integrity assurances are provided by robust networked software model augmented to commodity hardware and storage. Federated nature provides integrity assurance but also a lack of central control in that the accidental loss of multiple caches is unlikely but e.g. scheduled maintenance or upgrades could coincidentally collide.

====Chronopolis====
# ...
====MicroSoft Azure====
# ...
====Amazon S3/EC2====
# ...

==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

===Responses to questions===

====[[NDSA:Florida Center for Library Automation]]====

====[[NDSA:Harvard Library]]====

====[[NDSA:HathiTrust]]====

====[[NDSA:National Library of Medicine Responses]]====

====[[NDSA:Penn State]]====

====[[NDSA:WGBH Responses]]====

====[[NDSA:NYU Response]]====

====[[NDSA:Library of Congress]]====

====[[NDSA:Columbia University]]====

==General Concerns==
# confidential data
# encrypted data
# auditing
# preservation risks
# legal compliance
# ...

==Solution Models and Environments==
{| border="1"
!Name
!Offered as Service
!Deployed Locally
!Opensource
!Authentication Scheme
!Ingest Mechanism
!Export Mechanism
!Integrity/Validation Mechanism
!Replication Mechanism
!Administration Model (Federated, etc.)
!Tiering Support
|-
|iRODS
|
|
|
|
|
|
|
|
|
|
|-
|DuraCloud
|yes
|yes
|yes (Apache2)
|Basic Auth
|1:web-ui, 2:client-side utility, 3:REST-API
|1:web-ui, 2:client-side utility, 3:REST-API
|Checksum verified on ingest. On-demand checksum verification service.
|Built-in support for cross-cloud replication.
|
|
|-
|MetaArchive/GDDP
|
|
|
|
|
|
|
|
|
|
|-
|Chronopolis
|
|
|
|
|
|
|
|
|
|
|-
|Microsoft Azure
|
|
|
|
|
|
|
|
|
|
|-
|Amazon S3/EC2
|
|
|
|
|
|
|
|
|
|
|-
|}

NDSA:Cloud Presentations

2011-06-08T18:43:55Z

Rtc: /* Columbia University */

In each case we would want to identify who would present, who will contact them. Then when they will present.

From there we can include specific questions we would like them to respond to.

==Presentation Schedule and Slides==
# Feb 1, Tues, 1:00 EST call with iRods Reagan Moore ([[NDSA:Media:NIAID.ppt|presentation]])
# Feb 14, Monday, 11:00 EST call with Duracloud ([[NDSA:Media:DuracloudNDSA.ppt|presentation]])
# Feb 17, Thurs, 11:00 EST call with MetaArchive/GDDP Katherine Skinner, Matt Schultz and Martin Halbert MetaArchive NDSA ([[NDSA:Media:MetaArchive NDSA Infrastructure.ppt|presentation]])

==People/Projects to Contact==
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Questions for Cloud Service Presenters==
Here we are working on a set of general questions for presenters to develop talks around.

# What sort of use cases is your system designed to support? What doesn't this support?
# What preservation standards would your system support?
# What resources are required to support a solution implemented in your environment?
# What infrastructure do you rely on?
# How can your system impact digital preservation activities?
# If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
# What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice

===Responses to questions===
====[[NDSA:iRODS]] direct responses====

Other general notes:

* [Snavely] The need for each storage target to support a specific set of operations, and consistently with other storage targets, seems like a risk that comes along with the elegant abstraction that iRODS provides. Clear specifications help mitigate this risk.

====[[NDSA:DuraCloud]] direct responses====
Other general notes:

* [Snavely] Treatment of cloud provider is generally as a black box, without a strong sense of actual reliability of underlying storage systems. Cloud providers tend to promise checksum validation of contents, but recourse if validation fails was unknown (right?). Additional checksum validation has been augmented on top of cloud storage service by Duracloud.

====[[NDSA:MetaArchive/GDDP]] direct responses====
Other general notes:

* [Snavely] Built on LOCKSS, so data integrity assurances are provided by robust networked software model augmented to commodity hardware and storage. Federated nature provides integrity assurance but also a lack of central control in that the accidental loss of multiple caches is unlikely but e.g. scheduled maintenance or upgrades could coincidentally collide.

====Chronopolis====
# ...
====MicroSoft Azure====
# ...
====Amazon S3/EC2====
# ...

==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

===Responses to questions===

====[[NDSA:Florida Center for Library Automation]]====

====[[NDSA:Harvard Library]]====

====[[NDSA:HathiTrust]]====

====[[NDSA:National Library of Medicine Responses]]====

====[[NDSA:Penn State]]====

====[[NDSA:WGBH Responses]]====

====[[NDSA:NYU Response]]====

====[[NDSA:Library of Congress]]====

====[[NDSA:Columbia University]]====

==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

====[[NDSA:Your Institution Here]]====

==General Concerns==
# confidential data
# encrypted data
# auditing
# preservation risks
# legal compliance
# ...

==Solution Models and Environments==
{| border="1"
!Name
!Offered as Service
!Deployed Locally
!Opensource
!Authentication Scheme
!Ingest Mechanism
!Export Mechanism
!Integrity/Validation Mechanism
!Replication Mechanism
!Administration Model (Federated, etc.)
!Tiering Support
|-
|iRODS
|
|
|
|
|
|
|
|
|
|
|-
|DuraCloud
|yes
|yes
|yes (Apache2)
|Basic Auth
|1:web-ui, 2:client-side utility, 3:REST-API
|1:web-ui, 2:client-side utility, 3:REST-API
|Checksum verified on ingest. On-demand checksum verification service.
|Built-in support for cross-cloud replication.
|
|
|-
|MetaArchive/GDDP
|
|
|
|
|
|
|
|
|
|
|-
|Chronopolis
|
|
|
|
|
|
|
|
|
|
|-
|Microsoft Azure
|
|
|
|
|
|
|
|
|
|
|-
|Amazon S3/EC2
|
|
|
|
|
|
|
|
|
|
|-
|}

NDSA:Cloud Presentations

2011-06-08T18:43:34Z

Rtc:

In each case we would want to identify who would present, who will contact them. Then when they will present.

From there we can include specific questions we would like them to respond to.

==Presentation Schedule and Slides==
# Feb 1, Tues, 1:00 EST call with iRods Reagan Moore ([[NDSA:Media:NIAID.ppt|presentation]])
# Feb 14, Monday, 11:00 EST call with Duracloud ([[NDSA:Media:DuracloudNDSA.ppt|presentation]])
# Feb 17, Thurs, 11:00 EST call with MetaArchive/GDDP Katherine Skinner, Matt Schultz and Martin Halbert MetaArchive NDSA ([[NDSA:Media:MetaArchive NDSA Infrastructure.ppt|presentation]])

==People/Projects to Contact==
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Questions for Cloud Service Presenters==
Here we are working on a set of general questions for presenters to develop talks around.

# What sort of use cases is your system designed to support? What doesn't this support?
# What preservation standards would your system support?
# What resources are required to support a solution implemented in your environment?
# What infrastructure do you rely on?
# How can your system impact digital preservation activities?
# If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
# What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice

===Responses to questions===
====[[NDSA:iRODS]] direct responses====

Other general notes:

* [Snavely] The need for each storage target to support a specific set of operations, and consistently with other storage targets, seems like a risk that comes along with the elegant abstraction that iRODS provides. Clear specifications help mitigate this risk.

====[[NDSA:DuraCloud]] direct responses====
Other general notes:

* [Snavely] Treatment of cloud provider is generally as a black box, without a strong sense of actual reliability of underlying storage systems. Cloud providers tend to promise checksum validation of contents, but recourse if validation fails was unknown (right?). Additional checksum validation has been augmented on top of cloud storage service by Duracloud.

====[[NDSA:MetaArchive/GDDP]] direct responses====
Other general notes:

* [Snavely] Built on LOCKSS, so data integrity assurances are provided by robust networked software model augmented to commodity hardware and storage. Federated nature provides integrity assurance but also a lack of central control in that the accidental loss of multiple caches is unlikely but e.g. scheduled maintenance or upgrades could coincidentally collide.

====Chronopolis====
# ...
====MicroSoft Azure====
# ...
====Amazon S3/EC2====
# ...

==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, why did you choose these particular technologies?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements? Further, why are these your particular requirements?
#What storage media have you elected to use? (Disk, Tape, etc) Further, why did you choose these particular media?
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another? Further, what is it that prompts you to make these migrations?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?

===Responses to questions===

====[[NDSA:Florida Center for Library Automation]]====

====[[NDSA:Harvard Library]]====

====[[NDSA:HathiTrust]]====

====[[NDSA:National Library of Medicine Responses]]====

====[[NDSA:Penn State]]====

====[[NDSA:WGBH Responses]]====

====[[NDSA:NYU Response]]====

====[[NDSA:Library of Congress]]====

====[[NDSA:Columbia University]]====
====[[NDSA:Your Institution Here]]====

==General Concerns==
# confidential data
# encrypted data
# auditing
# preservation risks
# legal compliance
# ...

==Solution Models and Environments==
{| border="1"
!Name
!Offered as Service
!Deployed Locally
!Opensource
!Authentication Scheme
!Ingest Mechanism
!Export Mechanism
!Integrity/Validation Mechanism
!Replication Mechanism
!Administration Model (Federated, etc.)
!Tiering Support
|-
|iRODS
|
|
|
|
|
|
|
|
|
|
|-
|DuraCloud
|yes
|yes
|yes (Apache2)
|Basic Auth
|1:web-ui, 2:client-side utility, 3:REST-API
|1:web-ui, 2:client-side utility, 3:REST-API
|Checksum verified on ingest. On-demand checksum verification service.
|Built-in support for cross-cloud replication.
|
|
|-
|MetaArchive/GDDP
|
|
|
|
|
|
|
|
|
|
|-
|Chronopolis
|
|
|
|
|
|
|
|
|
|
|-
|Microsoft Azure
|
|
|
|
|
|
|
|
|
|
|-
|Amazon S3/EC2
|
|
|
|
|
|
|
|
|
|
|-
|}

NDSA:Infrastructure Working Group Members

2011-06-08T18:40:57Z

Rtc:

*Micah Altman
*Elizabeth Perkes
*Bryan Beecher
*Priscilla Caplan
*Karen Cariani
*Kris Carpenter
*Robert Cartolano
*Patricia Cruse
*Daphane DeLeon
*Blane Dessy
*Daniel Dodge
*Erin Engle
*Dean Farrell
*Eileen Fenton
*Michelle Gallinger
*Michael J. Giarlo
*Andrea Goethals
*Abbie Grotke
*Matt Guzzi
*Martin Halbert
*Christine Marie Hopper
*Bob Horton
*Howard, Barrie
*Martin Jacobson
*Joseph JaJa
*Leslie Johnston
*Jimi Jones
*Butch Lazorchak
*Cal Lee
*Jane Mandelbaum
*Jonathan Marmor
*David Minor
*Eugene Mopsik
*Michael Nelson
*Trevor Owens
*Joseph Pawletko
*Abbey Potter
*Curtis Pulford
*Patricia Smith-Mansfield
*Mike Smorul
*Cory Snavely
*Herbert Van de Sompel
*John Spencer
*Taylor Surface
*John Unsworth
*William Ying
*Andrew Woods
*Gene Hurr