NDSA:Cloud Presentations - Revision history

Nowviskie: adding logo

2016-11-29T21:59:20Z

adding logo

← Older revision		Revision as of 17:59, 29 November 2016
Line 1:		Line 1:
			[[File:NDSA Logo.png\|thumb]]
	In each case we would want to identify who would present, who will contact them. Then when they will present.		In each case we would want to identify who would present, who will contact them. Then when they will present.

Dlfadm: 72 revisions imported: Migrate NDSA content from Library of Congress

2016-02-11T19:18:13Z

72 revisions imported: Migrate NDSA content from Library of Congress

← Older revision	Revision as of 15:18, 11 February 2016
(No difference)

Trow: Moved the large scale storage questions and answers to their own page.

2012-08-24T14:50:40Z

Moved the large scale storage questions and answers to their own page.

← Older revision		Revision as of 10:50, 24 August 2012
Line 43:		Line 43:
	* [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.		* [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.

	~~==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:Harvard IQSS - DVN/Murray Archive]]====~~

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

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

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

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

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

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

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

	==Solution Models and Environments==		==Solution Models and Environments==

Trow: /* General Concerns */

2011-12-21T15:41:57Z

General Concerns

← Older revision		Revision as of 11:41, 21 December 2011
Line 79:		Line 79:

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

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

	==Solution Models and Environments==		==Solution Models and Environments==

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

2011-12-21T15:41:09Z

Questions for Member Institution Implementations of Large Scale Storage Architectures

← Older revision		Revision as of 11:41, 21 December 2011
Line 79:		Line 79:

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

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

	==General Concerns==		==General Concerns==

Trow: /* General Questions for Cloud Service Presenters */

2011-12-21T15:40:39Z

General Questions for Cloud Service Presenters

← Older revision		Revision as of 11:40, 21 December 2011
Line 42:		Line 42:

	* [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.		* [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==		==Questions for Member Institution Implementations of Large Scale Storage Architectures==

Micah altman: /* Solution Models and Environments */

2011-07-20T14:21:12Z

Solution Models and Environments

← Older revision		Revision as of 10:21, 20 July 2011
Line 120:		Line 120:
	\|Integrity/Validation Mechanism		\|Integrity/Validation Mechanism
	\|Replication Mechanism		\|Replication Mechanism
	\|Administration Model (Federated, etc.)		\|Content Administration Model (Federated, etc.)
	\|Tiering Support		\|Tiering Support
			\|Certifications
	\|-		\|-
	\|DuraCloud		\|DuraCloud
Line 132:		Line 133:
	\|Checksum verified on ingest. On-demand checksum verification service.		\|Checksum verified on ingest. On-demand checksum verification service.
	\|Built-in support for cross-cloud replication.		\|Built-in support for cross-cloud replication.
	\|		\|Local
	\|		\|No
	\|-		\|-
	\|MetaArchive/GDDP		\|MetaArchive/GDDP
	\|~~Offered as Service~~		\|Mixed - PLN service layer on top of local LOCKSS nodes
	\|~~Deployed Locally~~		\|Mixed - PLN service layer on top of local LOCKSS nodes
	\|~~Opensource~~		\|No
	\|~~Authentication Scheme~~		\|IP-based
	\|~~Ingest Mechanism~~		\|LOCKSS harvesting plugins
	\|~~Export Mechanism~~		\|LOCKSS web proxy
	\|~~Integrity/Validation Mechanism~~		\|LOCKSS distributed integrity checking
	\|~~Replication Mechanism~~		\|LOCKSS P2P
	\|~~Administration Model (Federated, etc.)~~		\|Single superuser across all nodes
	\|~~Tiering Support~~		\|No
	\|-		\|-
	\|Chronopolis		\|Chronopolis
	\|~~Offered as Service~~		\|Yes
	\|~~Deployed Locally~~		\|No
	\|~~Opensource~~		\|No
	\|~~Authentication Scheme~~		\|SRB/Irods based
	\|~~Ingest Mechanism~~		\|SRB/Irods based
	\|~~Export Mechanism~~		\|SRB/Irods based
	\|~~Integrity/Validation Mechanism~~		\|Local checksums
	\|~~Replication Mechanism~~		\|SRB/Irods
	\|~~Administration Model (Federated, etc.)~~		\|Single superuser
	\|~~Tiering Support~~		\|No
	\|-		\|-
	\|Microsoft Azure		\|Microsoft Azure
	\|~~Offered as Service~~		\|Yes
	\|~~Deployed Locally~~		\|No
	\|~~Opensource~~		\|No
	\|~~Authentication Scheme~~		\|Multiple
	\|~~Ingest Mechanism~~		\| .Net/WIF
	\|~~Export Mechanism~~		\| Multiple APIs, .Net
	\|~~Integrity~~/~~Validation Mechanism~~		\|Not known/propietary
	\|~~Replication Mechanism~~		\|Not known/propietary
	\|~~Administration Model (Federated, etc.)~~		\|Single super user
	\|~~Tiering Support~~		\|Not known/propietary
	\|-		\|-
	\|Amazon S3/EC2		\|Amazon S3/EC2
	\|~~Offered as Service~~		\|Yes
	\|~~Deployed Locally~~		\|No
	\|Opensource		\|Opensource
	\|~~Authentication Scheme~~		\|Multiple, including certs; proprietary / limited delegation model
	\|~~Ingest Mechanism~~		\|Restful API's
	\|~~Export Mechanism~~		\|Restful API's
	\|~~Integrity/Validation Mechanism~~		\|Proprietary
	\|~~Replication Mechanism~~		\|Proprietary
	\|~~Administration Model (Federated, etc.)~~		\|Single superuser
	\|~~Tiering Support~~		\|Yes
	\|-		\|-
	\|~~Dataverse Network\|~~		\|DVN/Safearchive
	\|~~Offered as Service~~		\|Yes
	\|~~Deployed Locally~~		\|Yes
	\|Opensource		\|Opensource
	\|~~Authentication Scheme~~		\|Basic Auth/IP
	\|~~Ingest Mechanism~~		\|Proprietary UI/Batch UI/LOCKSS harvesting plugins
	\|~~Export Mechanism~~		\|OAI/Lockss harvesting/proprietary
	~~\|Integrity~~/~~Validation Mechanism~~		\|LOCKS distributed integrity checks with additional TRAC auditing layer
	~~\|Replication Mechanism~~		\|LOCKS with additional TRAC-based provisioning layer
	~~\|Administration Model (Federated, etc.)~~		\|Federated & distributed
	\|~~Tiering Support~~		\|No
	\|-
	\|~~LOCKSS Public Network~~
	~~\|Offered as Service~~
	~~\|Deployed Locally~~
	~~\|Opensource~~
	~~\|Authentication Scheme~~
	~~\|Ingest Mechanism~~
	~~\|Export Mechanism~~
	~~\|Integrity/Validation Mechanism~~
	~~\|Replication Mechanism~~
	~~\|Administration Model (~~Federated~~, etc.)~~
	\|~~Tiering Support~~
	\|-		\|-
	\|}		\|}

Micah altman: /* Solution Models and Environments */

2011-07-20T14:07:19Z

Solution Models and Environments

← Older revision		Revision as of 10:07, 20 July 2011
Line 136:		Line 136:
	\|-		\|-
	\|MetaArchive/GDDP		\|MetaArchive/GDDP
	\|		\|Offered as Service
	\|		\|Deployed Locally
	\|		\|Opensource
	\|		\|Authentication Scheme
	\|		\|Ingest Mechanism
	\|		\|Export Mechanism
	\|		\|Integrity/Validation Mechanism
	\|		\|Replication Mechanism
	\|		\|Administration Model (Federated, etc.)
	\|		\|Tiering Support
	\|-		\|-
	\|Chronopolis		\|Chronopolis
	\|		\|Offered as Service
	\|		\|Deployed Locally
	\|		\|Opensource
	\|		\|Authentication Scheme
	\|		\|Ingest Mechanism
	\|		\|Export Mechanism
	\|		\|Integrity/Validation Mechanism
	\|		\|Replication Mechanism
	\|		\|Administration Model (Federated, etc.)
	\|		\|Tiering Support
	\|-		\|-
	\|Microsoft Azure		\|Microsoft Azure
	\|		\|Offered as Service
	\|		\|Deployed Locally
	\|		\|Opensource
	\|		\|Authentication Scheme
	\|		\|Ingest Mechanism
	\|		\|Export Mechanism
	\|		\|Integrity/Validation Mechanism
	\|		\|Replication Mechanism
	\|		\|Administration Model (Federated, etc.)
	\|		\|Tiering Support
	\|-		\|-
	\|Amazon S3/EC2		\|Amazon S3/EC2
	\|		\|Offered as Service
	\|		\|Deployed Locally
	\|		\|Opensource
	\|		\|Authentication Scheme
	\|		\|Ingest Mechanism
	\|		\|Export Mechanism
	\|		\|Integrity/Validation Mechanism
	\|		\|Replication Mechanism
	\|		\|Administration Model (Federated, etc.)
	\|		\|Tiering Support
	\|-		\|-
	\|Dataverse Network\|		\|Dataverse Network\|
	\|		\|Offered as Service
	\|		\|Deployed Locally
	\|		\|Opensource
	\|		\|Authentication Scheme
	\|		\|Ingest Mechanism
	\|		\|Export Mechanism
	\|		\|Integrity/Validation Mechanism
	\|		\|Replication Mechanism
	\|		\|Administration Model (Federated, etc.)
			\|Tiering Support
	\|-		\|-
	\|LOCKSS		\|LOCKSS Public Network
	\|		\|Offered as Service
	\|		\|Deployed Locally
	\|		\|Opensource
	\|		\|Authentication Scheme
	\|		\|Ingest Mechanism
	\|		\|Export Mechanism
	\|		\|Integrity/Validation Mechanism
	\|		\|Replication Mechanism
	\|		\|Administration Model (Federated, etc.)
	\|		\|Tiering Support
	\|-		\|-
	\|}		\|}

Micah altman: /* Solution Models and Environments */

2011-07-20T14:05:47Z

Solution Models and Environments

← Older revision		Revision as of 10:05, 20 July 2011
Line 112:		Line 112:
	\|-		\|-
	\|iRODS		\|iRODS
	\|		\|Offered as Service
	\|		\|Deployed Locally
	\|		\|Opensource
	\|		\|Authentication Scheme
	\|		\|Ingest Mechanism
	\|		\|Export Mechanism
	\|		\|Integrity/Validation Mechanism
	\|		\|Replication Mechanism
	\|		\|Administration Model (Federated, etc.)
	\|		\|Tiering Support
	\|-		\|-
	\|DuraCloud		\|DuraCloud
Line 172:		Line 172:
	\|-		\|-
	\|Amazon S3/EC2		\|Amazon S3/EC2
			\|
			\|
			\|
			\|
			\|
			\|
			\|
			\|
			\|
			\|
			\|-
			\|Dataverse Network\|
			\|
			\|
			\|
			\|
			\|
			\|
			\|
			\|
			\|
			\|-
			\|LOCKSS
	\|		\|
	\|		\|

Micah altman: /* ==Harvard IQSS - DVN/Murray Archive */

2011-07-20T13:49:30Z

==Harvard IQSS - DVN/Murray Archive

← Older revision		Revision as of 09:49, 20 July 2011
Line 71:		Line 71:
	====[[NDSA:Harvard Library]]====		====[[NDSA:Harvard Library]]====

	====[[NDSA:Harvard IQSS - DVN/Murray Archive]]==		====[[NDSA:Harvard IQSS - DVN/Murray Archive]]====

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