DLF Wiki - User contributions [en]

NDSA:Cloud Presentations

2011-04-04T21:55:44Z

Lesliej: /* iRODS direct responses */

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

==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, which service providers or tools did you consider and how did you make your choice?
#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?
#What storage media have you elected to use? (Disk, Tape, etc)
#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?
# 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: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====
# ...

==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:IRODS

2011-04-04T21:55:18Z

Lesliej: Created page with '# What sort of use cases is your system designed to support? What doesn't this support? ## Share Data ## Build Digital Libraries ## Build a Preservation Environment ## Any group…'

# What sort of use cases is your system designed to support? What doesn't this support?
## Share Data
## Build Digital Libraries
## Build a Preservation Environment
## Any group that needs to manage distributed data or to migrate data should consider iRODS.
Question: Is this a system or a prototype? Answer: It is definitely in production, although there is a separate prototype for NARA.

Question: Who is using it for a preservation use case? Answer: CDR and the Taiwan National Archive
# What preservation strategies would your system support?
## The principle strategy is the instantiation of a standard set of enforceable policies in a preservation archive.
## 120 policies have been identified to date. In identifying and reviewing the policies at a SAA workshop, there was a subset of 20 that at least 50% wanted. there is a long tail of policies that at least 1 organization wanted.
Question: What issues are there of mismatched semantics across system? Answer: An example is NCAR, with mass storage form the 1960s that understood tape get/put. A disk cache had to be put in place on top of tape to interact with. It's the same with Cloud services, which also deals in get/put, and need a cache on top.

Question: What is the base level of functionality to be a part of iRODS? Answer: This varies. There are specific functions for each local environment. What data processing needs are there? Where must they be run? etc.

Question: When managing large data collections, is distributed data integrity checking built into the system? Answer: Yes, at the whichever locations where the data is stored. You can create procedures for independent checking.
# What infrastructure do you rely on? AND What resources are required to support a solution implemented in your environment?
## Any operating system
## Up to 1 million files cam run in a standalone instance
## Over 1 million files, a distributed system is needed.
## The number of files is the primary gating factor for the database. There is use with Postgres, MySQL, and Oracle, but most use Postgres.
Question: What is the largest current installation? Answer: NASA, with 700 TB, 65-85 million files. A Particle data project in France has 2-3 PB.
Question: Why is the catalog in one central location? Answer: Efficiency. There are three models in use in various installations. NIH required a central catalog, which can have slaves. NAO required multiple chained into a catalog. A project in the UK is using multiple Grids chained together.

Question: Are there any moving image projects? Answer: Yes, Cinegrid. Also an ocean observation project with video observation files.
# How can the cloud environment impact digital preservation activities?
## There are no assertions about integrity or any properties. The system has to independently record and assert.
## Once a project reaches a certain amount of data, it should really work locally, not in the cloud. It can be more cost efficient/predictable if you expect to be running within local capacity.
# If we put data in your system today what systems and processes are in place so that we can get it back 50 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
## In 50 years, NONE of our current infrastructure components will still be in place.
## We need infrastructure independence - we have to be able to migrate based on policies, not a specific infrastructure, to a new infrastructure.
## To do that, we must know all previous versions of policies, and which are applied to which objects. That is potentially easiest with a policy-based system like iRODS.
Question: What cloud services are supported so far? Answer: S3 and EC3. It can also be run in a virtualized environment, such as the VCL project at NCSU.

Question: What about distributed checksums? Answer: Can check in each and/or compare across multiple copies. In a local environment, it checks against the central catalog.

Question: Are there any privacy use cases to be aware of? Answer: They have worked with a group on IRB issues, and can implement policies against a local IRB catalog. That data is NOT stored in the central catalog.
# Anything else?
## The next release is February 2011.

NDSA:Cloud Presentations

2011-04-04T21:17:32Z

Lesliej: /* iRODS */

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

==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, which service providers or tools did you consider and how did you make your choice?
#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?
#What storage media have you elected to use? (Disk, Tape, etc)
#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?
# 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: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====
# ...

==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-02-01T19:09:04Z

Lesliej: /* People/Projects to Contact */

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==
Once we start scheduling presenters we will keep a list of the talks here.

==People/Projects to Contact==
*DuraCloud/Duraspace (Leslie to contact)
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation http://www.metaarchive.org/GDDP (Martin will contact)
*Irods: Reagan Moore, 2/1/2011
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Guiding Questions for 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 strategies or standards would your system support?
*What resources are required to support a solution implemented in your environment
*How can the cloud environment 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 50 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
*What infrastructure do you rely on?

NDSA:Cloud Presentations

2011-02-01T19:08:49Z

Lesliej: /* People/Projects to Contact */

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==
Once we start scheduling presenters we will keep a list of the talks here.

==People/Projects to Contact==
*DuraCloud/Duraspace (Leslie to contact)
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation http://www.metaarchive.org/GDDP (Martin will contact)
*Irods 2/1/2011
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Guiding Questions for 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 strategies or standards would your system support?
*What resources are required to support a solution implemented in your environment
*How can the cloud environment 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 50 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
*What infrastructure do you rely on?

NDSA:Infrastructure Working Group Members

2011-01-20T22:09:54Z

Lesliej:

*Micah Altman
*Joseph Pawletko
*Elizabeth Perkes
*Bryan Beecher
*Karen Cariani
*Kris Carpenter
*Patricia Cruse
*Daphane DeLeon
*Blane Dessy
*Daniel Dodge
*Erin Engle
*Dean Farrell
*Eileen Fenton
*Michelle Gallinger
*Michael J. Giarlo
*U 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
*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

NDSA:Tuesday, Jan 18, 2011

2011-01-20T22:02:23Z

Lesliej: Created page with 'NDSA Infrastructure call, 01/18/2011 On the call: *Karen Cariani *Leslie Johnston *Elizabeth Perkes *Cal Lee *Dan Dodge *Mike Smorul *Mike Giarlo *Micah Altman *Joe Pawletko *M…'

NDSA Infrastructure call, 01/18/2011

On the call:

*Karen Cariani
*Leslie Johnston
*Elizabeth Perkes
*Cal Lee
*Dan Dodge
*Mike Smorul
*Mike Giarlo
*Micah Altman
*Joe Pawletko
*Michelle Galliger
*Cory Snavely
*Curtis Pulford
*Trevor Owens
*Dean Farrell
*Taylor Surface
*Kris Carpenter
*Martin Halbert
*(Apologies to anyone we missed)

==Agenda==

*Determine if the third Tues of every month at 11:00 works best for the working group call
*Update of the NDSA meeting in December
*Wiki overview - discuss how we want to use it
*Discussion and planning to move forward with our two work issues

==Call Schedule==

It works for most people. Some have conflicts, but most can make it work.

==December 2010 NDSA Organizing Workshop==

Over 40 people were in the room, discussing how NDSA could and should be organized. It was a fruitful conversation, with a wide spectrum of views in some areas, with others very close to consensus. The [[NDSA:Organizing Workshop Notes]] have been circulated to the organizing group. There is a timeline for document review and ratification by all NDSA members:

*Send revised draft of organizing documents to all members: 2/04/11
*Review and comment period for documents: 2/18/11
*Incorporation of revisions from entire membership: 2/25/11
*Vote by entire membership for ratification: 3/01/11
*Voting period ends: 3/15/11

Please send comments to Michelle or use the wiki.

Kris: One point – During the meeting there was a lot of discussion about tightening down the focus of each working group. One specific topic was coordinating the participation of folks who are signed up for many groups.

Leslie: There will be some natural group membership fluctuations while people select the most appropriate group to be on.

==Using the Wiki==

Karen: Do all agree that we should use the wiki as a collaborative work space?

All: Yes, but we need to get notifications about new work by email.

Everyone should have an account (Michelle set them up). Log in to generate your password.
Your User Name will be the front part of your email address (for example, lesliej or abgr)
Then click on "email new password" and a password should be sent to you.

The working group charter we developed during our last call that will be guiding our work can be found on the wiki. It can be found here: [[NDSA:Infrastructure_Working_Group]]

Meeting notes are going up soon.

==Work==

The top topic from the Doodle poll the topic is:

* Investigate, recognize, and document potential preservation emerging practices in the use of large-scale storage and cloud infrastructures.

This one was a very close second so we should consider how we might address both:

* Investigate, share, and recognize emerging practices for use and development and sharing of open source tools and other software that enable digital preservation.

All: Let’s start with cloud storage. Let’s invite experts to speak with us.

Cal: What do we want to learn?

Martin: What are the issues in architecting systems? It is compelling that they can potentially grow seamlessly from small to very large capacity with the same functional capabilities. Can they really? What are the issues?

Kris: Are we asking about services offered by others, or about deploying our own cloud environments? It would be nice to hear about both.

All: Yes.

Unidentified speaker: We need to identify preservation issues for speakers to address. As an example, how will we deal with confidential information, encrypted files, and auditing? What are the preservation risks?

Who will we invite?

*DuraCloud (has worked with multiple commercial providers)
*Microsoft Azure
*Amazon (hosts a contest and shares best examples of use of the cloud)
*NSF (has been making awards around the use of Google and Azure clouds for computation)
*Chronopolis
*Irods
*LOCKSS
*Authors of the Guide to Distributed Digital Preservation

Trevor: Will we set up an Action Group?

All: No, not for this. It’s better as a full group activity.

Mike Smorul: Volunteers to talk about how they have worked with Chronopolis and Duraspace.

Martin: As one of the authors of the Guide to Distributed Digital Preservation, they are working on a follow-up. The folks continuing the work that could give a presentation.

Martin – will talk to Katherine Skinner, and Matt Schultz. (Did Martin also say he would talk to Stanford and LOCKSS)

Leslie: Will invite DuraCloud as the first speaker. Can also talk to Microsoft about Azure. DuraCloud team may be able to help us connect with commercial providers.

Cal: Will talk to Irods team.

Kris - Let’s not forget about personal archiving in the cloud. There are some Silicon Valley companies we might be able to connect with.

Cal: What questions do we need to ask of them to compare each of the different solutions?

Trevor: Suggests that we develop a set of questions as a group to give to presenter s before hand so that all the presenters have common questions.

==Draft Questions==

*What sort of use cases is your system designed to support? What doesn't this support?
*What preservation strategies or standards would your system support?
*What resources are required to support a solution implemented in your environment
*How can the cloud environment 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 50 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
*What infrastructure do you rely on?

Kris: There is also a lot of movement toward solutions for legal compliance. We should make sure to bring that up.

Martin: Did anything come out of the LOC _Preservation Storage meeting about the Cloud?

Leslie. Not so much. Will send link to meeting notes.

Martin: When we ask about standards, which do we mean? Do we know?

Cal: We need to find out what standards they are prioritizing.

Martin: If they don’t have an answer, that’s a red flag.

Karen: the [[NDSA:Cloud Presentations]] questions will go on the wiki.

NDSA:Cloud Presentations

2011-01-20T21:44:37Z

Lesliej: /* People/Projects to Contact */

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==
Once we start scheduling presenters we will keep a list of the talks here.

==People/Projects to Contact==
*DuraCloud/Duraspace (Leslie to contact)
*Chronopolis (Mike Smorul will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation http://www.metaarchive.org/GDDP (Martin will contact)
*Irods (Cal Lee will contact)
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Guiding Questions for 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 strategies or standards would your system support?
*What resources are required to support a solution implemented in your environment
*How can the cloud environment 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 50 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
*What infrastructure do you rely on?

NDSA:Cloud Presentations

2011-01-20T21:28:28Z

Lesliej: /* General Guiding Questions for Presenters */

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==
Once we start scheduling presenters we will keep a list of the talks here.

==People/Projects to Contact==
*DuraCloud/Duraspace (Leslie to contact)
*Chronopolis (Who will contact)
*Open questions from the Educopia Guide to Distributed Digital Preservation http://www.metaarchive.org/GDDP (Who will contact?)
*Irods (Kell will contact)
*Commercial providers? (Who specifically would we want here? Please add them.)
**Azure (Leslie to contact)
**Amazon (Who will contact?)

==General Guiding Questions for 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 strategies or standards would your system support?
*What resources are required to support a solution implemented in your environment
*How can the cloud environment 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 50 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
*What infrastructure do you rely on?