NDSA:Tuesday, Jan 28, 2014 - Revision history

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

2016-02-11T19:20:37Z

24 revisions imported: Migrate NDSA content from Library of Congress

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

Ltadic: /* Roster */

2014-01-30T04:29:52Z

Roster

← Older revision		Revision as of 00:29, 30 January 2014
Line 6:		Line 6:
	*Dave MacCarn, WGBH		*Dave MacCarn, WGBH
	*Jim Harper, PFA Inc.		*Jim Harper, PFA Inc.
	*Linda Tadic, Archive Network		*Linda Tadic, Audiovisual Archive Network
	*Joe Pawletko, New York University		*Joe Pawletko, New York University
	*Martin Jacobson, U.S. National Archives and Records Administration		*Martin Jacobson, U.S. National Archives and Records Administration

Bhow at 20:51, 29 January 2014

2014-01-29T20:51:08Z

← Older revision		Revision as of 16:51, 29 January 2014
Line 23:		Line 23:
	#Open suggestions for projects/programs/etc. to invite to present to the group. (Start thinking about these before the call if you have a few minutes.)		#Open suggestions for projects/programs/etc. to invite to present to the group. (Start thinking about these before the call if you have a few minutes.)
	#Kick off thinking about digital stewardship infrastructure issues to feature in the 2015 National Agenda for Digital Stewardship.		#Kick off thinking about digital stewardship infrastructure issues to feature in the 2015 National Agenda for Digital Stewardship.

			==Action Items==
			*Recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input - Trevor
			*Create a Google Doc and use it to identify cross-cutting themes to bring the four past presentations together more thematically in prepartion for a blog post - Trevor, Chelcie, Joe, Karen
			*Identify projects and speakers on digital preservation infrastructure for future calls - All
			*Think of ideas to include in the 2015 National Agenda - All

	==Discussion==		==Discussion==

Bhow: /* Roster */

2014-01-29T17:01:25Z

Roster

← Older revision		Revision as of 13:01, 29 January 2014
Line 15:		Line 15:
	*Kat Bell, Dance Heritage Coalition		*Kat Bell, Dance Heritage Coalition
	*Quyen Nguyen, U.S. National Archives and Records Administration		*Quyen Nguyen, U.S. National Archives and Records Administration
			*Gail Truman, Truman Technologies

	==Agenda==		==Agenda==

Bhow at 16:58, 29 January 2014

2014-01-29T16:58:08Z

← Older revision		Revision as of 12:58, 29 January 2014
Line 1:		Line 1:
	~~THESE NOTES ARE IN DRAFT NOW AND WILL BE UPDATED AND TIDIED UP WITHIN 48 HOURS, entered 20140128T15:00:00~~

	~~Every other call is a work meeting, and the others are for highlighting people working on digital stewardship.~~

	==Roster==		==Roster==
	*Trevor Owens, Library of Congress		*Trevor Owens, Library of Congress

Bhow: /* Discussion */

2014-01-29T16:55:51Z

Discussion

← Older revision		Revision as of 12:55, 29 January 2014
Line 37:		Line 37:

	The Coordinating Committee has requested that working groups begin discussing the update to the National Agenda. Are there any infrastructure issues that should be elevated to the national level. The Internet Archive and Olive Library have launched emulation environments, which take emulation from the research phase to implementation phase. Funding preservation activities and modles for long-term sustainabilty on a national level to raise awareness of the expense of long-term preservation. Managing and monitoring the health of your data. Metrics on what it takes for forward migration within specific storage environments, and spelling out benchmarking for format migration. File based fixity checks and frame level fixity checks remain the same, but what about when you change formats?		The Coordinating Committee has requested that working groups begin discussing the update to the National Agenda. Are there any infrastructure issues that should be elevated to the national level. The Internet Archive and Olive Library have launched emulation environments, which take emulation from the research phase to implementation phase. Funding preservation activities and modles for long-term sustainabilty on a national level to raise awareness of the expense of long-term preservation. Managing and monitoring the health of your data. Metrics on what it takes for forward migration within specific storage environments, and spelling out benchmarking for format migration. File based fixity checks and frame level fixity checks remain the same, but what about when you change formats?

			==Documents==
			[[File:NDSA Fixity Check Project Concept Draft v6 5.pdf]]

Bhow: /* Discussion */

2014-01-29T16:52:28Z

Discussion

← Older revision		Revision as of 12:52, 29 January 2014
Line 28:		Line 28:

	==Discussion==		==Discussion==
	#The fixity document has had a fair amount of comments on email. The document may not be appropriate for people that aren't familiar with specific terms. Is there a way to make it more accessible to people not that versed in digital preservation? Perhaps a brief intro document that links readers who require more information to resources with more in-depth coverage of a specific term. At least add a sentence to briefly define each PREMIS and TRAC, especially PREMIS because we lean on it as a definition up front. The intro information could link off to the Levels of Preservation, and other resources. There should be some language addressing how the data to be preserved was created and workflow information, and something on the kind of data you should keep about your fixity check like the tools you used, when the data was checked, the results, and what algorithm used. Where will this document live, and what is this document, e.g., a factsheet or a guidance document? Trevor will refer to a grey literature guide to recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input.		The fixity document has had a fair amount of comments on email. The document may not be appropriate for people that aren't familiar with specific terms. Is there a way to make it more accessible to people not that versed in digital preservation? Perhaps a brief intro document that links readers who require more information to resources with more in-depth coverage of a specific term. At least add a sentence to briefly define each PREMIS and TRAC, especially PREMIS because we lean on it as a definition up front. The intro information could link off to the Levels of Preservation, and other resources. There should be some language addressing how the data to be preserved was created and workflow information, and something on the kind of data you should keep about your fixity check like the tools you used, when the data was checked, the results, and what algorithm used. Where will this document live, and what is this document, e.g., a factsheet or a guidance document? Trevor will refer to a grey literature guide to recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input.

	#Joe and Karen tried to pull together a summary of the four talks, i.e., Islandora, Hydra, Archivematica and Open Planets, but they were all very different. There were some themes, e.g., open source as an ecosystem and the intersection of staffing and open source platforms. The goal was to attempt to pull out some cross-cutting themes to bring the presentations together more thematically, and publish a blog post on what the working group learned. The workng group decided they wanted to have these themed presentations together, although each presentation received a dedicated blog post on The Signal. Trevor, Chelcie, Joe, and Karen will attempt to work on this, and share via Google Doc before they bring it back to the larger group.		Joe and Karen tried to pull together a summary of the four talks, i.e., Islandora, Hydra, Archivematica and Open Planets, but they were all very different. There were some themes, e.g., open source as an ecosystem and the intersection of staffing and open source platforms. The goal was to attempt to pull out some cross-cutting themes to bring the presentations together more thematically, and publish a blog post on what the working group learned. The workng group decided they wanted to have these themed presentations together, although each presentation received a dedicated blog post on The Signal. Trevor, Chelcie, Joe, and Karen will attempt to work on this, and share via Google Doc before they bring it back to the larger group.

	#We've been chasing down a few stray respondants, who did not respond to the storage survey. After that is completed, then we'll have something to share with the greater group. This should happen in the near future.		We've been chasing down a few stray respondants, who did not respond to the storage survey. After that is completed, then we'll have something to share with the greater group. This should happen in the near future.

	#Are there projects that relate to digital preservation infrastructure that you think people should know about? It would be good to invite people from these projects to talk. Fedora 4 was recently released, and someone can talk about the improvements to Fedora 4. Open Stack is an OSS for running your own cloud compute system. There is a move to develop a public media platform, and there is a lot of talk aobut it. Karen can search around to see if someone can talk about it. It may be more about access than preservation, and more DPLA-ish than HathiTrust-ish? What about DPN? Ladd Hanson, University of Texas, and Tom Cramer, Stanford University, are DPN Team members. Katherine Skinner, Educopia Institute, can talk about MetaArchive that may address the needs of small- to medium-sized institutions with limited resources. Brad Westbrook could talk about ArchivesSpace. Email Trevor with any other suggestions as they occur to you.		Are there projects that relate to digital preservation infrastructure that you think people should know about? It would be good to invite people from these projects to talk. Fedora 4 was recently released, and someone can talk about the improvements to Fedora 4. Open Stack is an OSS for running your own cloud compute system. There is a move to develop a public media platform, and there is a lot of talk aobut it. Karen can search around to see if someone can talk about it. It may be more about access than preservation, and more DPLA-ish than HathiTrust-ish? What about DPN? Ladd Hanson, University of Texas, and Tom Cramer, Stanford University, are DPN Team members. Katherine Skinner, Educopia Institute, can talk about MetaArchive that may address the needs of small- to medium-sized institutions with limited resources. Brad Westbrook could talk about ArchivesSpace. Email Trevor with any other suggestions as they occur to you.

	#The Coordinating Committee has requested that working groups begin discussing the update to the National Agenda. Are there any infrastructure issues that should be elevated to the national level. The Internet Archive and Olive Library have launched emulation environments, which take emulation from the research phase to implementation phase. Funding preservation activities and modles for long-term sustainabilty on a national level to raise awareness of the expense of long-term preservation. Managing and monitoring the health of your data. Metrics on what it takes for forward migration within specific storage environments, and spelling out benchmarking for format migration. File based fixity checks and frame level fixity checks remain the same, but what about when you change formats?		The Coordinating Committee has requested that working groups begin discussing the update to the National Agenda. Are there any infrastructure issues that should be elevated to the national level. The Internet Archive and Olive Library have launched emulation environments, which take emulation from the research phase to implementation phase. Funding preservation activities and modles for long-term sustainabilty on a national level to raise awareness of the expense of long-term preservation. Managing and monitoring the health of your data. Metrics on what it takes for forward migration within specific storage environments, and spelling out benchmarking for format migration. File based fixity checks and frame level fixity checks remain the same, but what about when you change formats?

Bhow: /* Discussion */

2014-01-29T16:51:25Z

Discussion

← Older revision		Revision as of 12:51, 29 January 2014
Line 28:		Line 28:

	==Discussion==		==Discussion==
	The fixity document has had a fair amount of comments on email. The document may not be appropriate for people that aren't familiar with specific terms. Is there a way to make it more accessible to people not that versed in digital preservation? Perhaps a brief intro document that links readers who require more information to resources with more in-depth coverage of a specific term. At least add a sentence to briefly define each PREMIS and TRAC, especially PREMIS because we lean on it as a definition up front. The intro information could link off to the Levels of Preservation, and other resources. There should be some language addressing how the data to be preserved was created and workflow information, and something on the kind of data you should keep about your fixity check like the tools you used, when the data was checked, the results, and what algorithm used. Where will this document live, and what is this document, e.g., a factsheet or a guidance document? Trevor will refer to a grey literature guide to recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input.		#The fixity document has had a fair amount of comments on email. The document may not be appropriate for people that aren't familiar with specific terms. Is there a way to make it more accessible to people not that versed in digital preservation? Perhaps a brief intro document that links readers who require more information to resources with more in-depth coverage of a specific term. At least add a sentence to briefly define each PREMIS and TRAC, especially PREMIS because we lean on it as a definition up front. The intro information could link off to the Levels of Preservation, and other resources. There should be some language addressing how the data to be preserved was created and workflow information, and something on the kind of data you should keep about your fixity check like the tools you used, when the data was checked, the results, and what algorithm used. Where will this document live, and what is this document, e.g., a factsheet or a guidance document? Trevor will refer to a grey literature guide to recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input.

	Joe and Karen tried to pull together a summary of the four talks, i.e., Islandora, Hydra, Archivematica and Open Planets, but they were all very different. There were some themes, e.g., open source as an ecosystem and the intersection of staffing and open source platforms. The goal was to attempt to pull out some cross-cutting themes to bring the presentations together more thematically, and publish a blog post on what the working group learned. The workng group decided they wanted to have these themed presentations together, although each presentation received a dedicated blog post on The Signal. Trevor, Chelcie, Joe, and Karen will attempt to work on this, and share via Google Doc before they bring it back to the larger group.		#Joe and Karen tried to pull together a summary of the four talks, i.e., Islandora, Hydra, Archivematica and Open Planets, but they were all very different. There were some themes, e.g., open source as an ecosystem and the intersection of staffing and open source platforms. The goal was to attempt to pull out some cross-cutting themes to bring the presentations together more thematically, and publish a blog post on what the working group learned. The workng group decided they wanted to have these themed presentations together, although each presentation received a dedicated blog post on The Signal. Trevor, Chelcie, Joe, and Karen will attempt to work on this, and share via Google Doc before they bring it back to the larger group.

	We've been chasing down a few stray respondants, who did not respond to the storage survey. After that is completed, then we'll have something to share with the greater group. This should happen in the near future.		#We've been chasing down a few stray respondants, who did not respond to the storage survey. After that is completed, then we'll have something to share with the greater group. This should happen in the near future.

	Are there projects that relate to digital preservation infrastructure that you think people should know about~~. We can~~ invite ~~them~~ to talk. Fedora 4 is released, and someone can talk about the improvements to Fedora 4. Open Stack is an OSS for running your own cloud compute system. There is a move to ~~make~~ a public media platform, and there is a lot of talk aobut it. Karen can search ~~aournd~~ to see if ~~osmeone~~ can talk about it. It may be more about access than preservation, and ~~sort of~~ DPLA-ish or HathiTrust-ish? What about DPN, Ladd Hanson ~~from TX~~. Katherine Skinner can talk about MetaArchive. Brad Westbrook ~~form ArchiveSpace~~.		#Are there projects that relate to digital preservation infrastructure that you think people should know about? It would be good to invite people from these projects to talk. Fedora 4 was recently released, and someone can talk about the improvements to Fedora 4. Open Stack is an OSS for running your own cloud compute system. There is a move to develop a public media platform, and there is a lot of talk aobut it. Karen can search around to see if someone can talk about it. It may be more about access than preservation, and more DPLA-ish than HathiTrust-ish? What about DPN? Ladd Hanson, University of Texas, and Tom Cramer, Stanford University, are DPN Team members. Katherine Skinner, Educopia Institute, can talk about MetaArchive that may address the needs of small- to medium-sized institutions with limited resources. Brad Westbrook could talk about ArchivesSpace. Email Trevor with any other suggestions as they occur to you.

	The Coordinating Committee has requested ~~the~~ working groups begin discussing the update to the National Agenda. ~~Any~~ infrastructure issues that should be elevated to the national level. IA and Olive Library have launched emulation environments~~. Take it~~ from the research phase to implementation phase. Funding on a national level, and ~~metrics~~ on what it takes for forward migration within specific storage environments~~. What about when you change formats?~~		#The Coordinating Committee has requested that working groups begin discussing the update to the National Agenda. Are there any infrastructure issues that should be elevated to the national level. The Internet Archive and Olive Library have launched emulation environments, which take emulation from the research phase to implementation phase. Funding preservation activities and modles for long-term sustainabilty on a national level to raise awareness of the expense of long-term preservation. Managing and monitoring the health of your data. Metrics on what it takes for forward migration within specific storage environments, and spelling out benchmarking for format migration. File based fixity checks and frame level fixity checks remain the same, but what about when you change formats?

	~~4) projects to present to the group –Fedora 4 – new version, update~~,
	~~Open Stack – run your own infrastructure~~
	~~Public media platform~~
	~~Chronopolis~~
	~~DPN~~
	~~Something for smaller archives~~ and ~~institutions to share services~~
	~~MetaArchive – Catherine Skinner~~
	~~Archives Space – Brad Westford~~

	~~5) National Agenda – moving to implementation stage~~
	funding preservation activities – models for long term sustainability – managing and monitoring the health of your data. Raise consciousness of the expense of these efforts. Not necessarily cheaper…..get some metrics to migrate file forward – what does it take. Spelling out benchmarking ~~and metrics~~ for format migration. File based fixity checks and frame level fixity ~~check for moving images. Migrate file format forward – frame level check should~~ remain the same.

Bhow: /* Discussion */

2014-01-29T16:27:32Z

Discussion

← Older revision		Revision as of 12:27, 29 January 2014
Line 30:		Line 30:
	The fixity document has had a fair amount of comments on email. The document may not be appropriate for people that aren't familiar with specific terms. Is there a way to make it more accessible to people not that versed in digital preservation? Perhaps a brief intro document that links readers who require more information to resources with more in-depth coverage of a specific term. At least add a sentence to briefly define each PREMIS and TRAC, especially PREMIS because we lean on it as a definition up front. The intro information could link off to the Levels of Preservation, and other resources. There should be some language addressing how the data to be preserved was created and workflow information, and something on the kind of data you should keep about your fixity check like the tools you used, when the data was checked, the results, and what algorithm used. Where will this document live, and what is this document, e.g., a factsheet or a guidance document? Trevor will refer to a grey literature guide to recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input.		The fixity document has had a fair amount of comments on email. The document may not be appropriate for people that aren't familiar with specific terms. Is there a way to make it more accessible to people not that versed in digital preservation? Perhaps a brief intro document that links readers who require more information to resources with more in-depth coverage of a specific term. At least add a sentence to briefly define each PREMIS and TRAC, especially PREMIS because we lean on it as a definition up front. The intro information could link off to the Levels of Preservation, and other resources. There should be some language addressing how the data to be preserved was created and workflow information, and something on the kind of data you should keep about your fixity check like the tools you used, when the data was checked, the results, and what algorithm used. Where will this document live, and what is this document, e.g., a factsheet or a guidance document? Trevor will refer to a grey literature guide to recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input.

	Joe and Karen tried to pull together a summary of the four talks, i.e., Islandora, Hydra, Archivematica and Open Planets, but they were all very different. There were some themes, e.g., open source as an ecosystem and the intersection of staffing and open source platforms. The goal was to publish a blog post on what the working group learned~~, and bring the presentations together more thematically~~. The workng group decided they wanted to have these themed presentations together~~. Because their were~~ blog ~~posts~~ on The Signal~~, they have been reported out. There was an attempt to pull out some cross-cutting themes, though~~. Trevor, Chelcie, Joe and Karen will attempt to work on this, and share via Google Doc before they bring it back to the larger group.		Joe and Karen tried to pull together a summary of the four talks, i.e., Islandora, Hydra, Archivematica and Open Planets, but they were all very different. There were some themes, e.g., open source as an ecosystem and the intersection of staffing and open source platforms. The goal was to attempt to pull out some cross-cutting themes to bring the presentations together more thematically, and publish a blog post on what the working group learned. The workng group decided they wanted to have these themed presentations together, although each presentation received a dedicated blog post on The Signal. Trevor, Chelcie, Joe, and Karen will attempt to work on this, and share via Google Doc before they bring it back to the larger group.

	We've been chasing down a few stray respondants, ~~but in~~ the ~~near future~~ we'll have something to share with the greater group.		We've been chasing down a few stray respondants, who did not respond to the storage survey. After that is completed, then we'll have something to share with the greater group. This should happen in the near future.

	Are there projects that relate to digital preservation infrastructure that you think people should know about. We can invite them to talk. Fedora 4 is released, and someone can talk about the improvements to Fedora 4. Open Stack is an OSS for running your own cloud compute system. There is a move to make a public media platform, and there is a lot of talk aobut it. Karen can search aournd to see if osmeone can talk about it. It may be more about access than preservation, and sort of DPLA-ish or HathiTrust-ish? What about DPN, Ladd Hanson from TX. Katherine Skinner can talk about MetaArchive. Brad Westbrook form ArchiveSpace.		Are there projects that relate to digital preservation infrastructure that you think people should know about. We can invite them to talk. Fedora 4 is released, and someone can talk about the improvements to Fedora 4. Open Stack is an OSS for running your own cloud compute system. There is a move to make a public media platform, and there is a lot of talk aobut it. Karen can search aournd to see if osmeone can talk about it. It may be more about access than preservation, and sort of DPLA-ish or HathiTrust-ish? What about DPN, Ladd Hanson from TX. Katherine Skinner can talk about MetaArchive. Brad Westbrook form ArchiveSpace.

	The Coordinating Committee has requested the working groups begin discussing the update to the National Agenda. Any infrastructure issues that should be elevated to the national level. IA and Olive Library have launched emulation environments. Take it from the research phase to implementation phase. Funding on a national level, and metrics on what it takes for forward migration within specific storage environments. What about when you change formats?		The Coordinating Committee has requested the working groups begin discussing the update to the National Agenda. Any infrastructure issues that should be elevated to the national level. IA and Olive Library have launched emulation environments. Take it from the research phase to implementation phase. Funding on a national level, and metrics on what it takes for forward migration within specific storage environments. What about when you change formats?

	~~2) Work on a google doc trying to highlight the themes and use the conversation as highlights and examples. Karen, Joe, Trevor -Chelsea has also offered to help.~~

	~~3) NDSA storage survey update –~~

	4) projects to present to the group –Fedora 4 – new version, update,		4) projects to present to the group –Fedora 4 – new version, update,

Bhow: /* Discussion */

2014-01-29T16:16:15Z

Discussion

← Older revision		Revision as of 12:16, 29 January 2014
Line 30:		Line 30:
	The fixity document has had a fair amount of comments on email. The document may not be appropriate for people that aren't familiar with specific terms. Is there a way to make it more accessible to people not that versed in digital preservation? Perhaps a brief intro document that links readers who require more information to resources with more in-depth coverage of a specific term. At least add a sentence to briefly define each PREMIS and TRAC, especially PREMIS because we lean on it as a definition up front. The intro information could link off to the Levels of Preservation, and other resources. There should be some language addressing how the data to be preserved was created and workflow information, and something on the kind of data you should keep about your fixity check like the tools you used, when the data was checked, the results, and what algorithm used. Where will this document live, and what is this document, e.g., a factsheet or a guidance document? Trevor will refer to a grey literature guide to recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input.		The fixity document has had a fair amount of comments on email. The document may not be appropriate for people that aren't familiar with specific terms. Is there a way to make it more accessible to people not that versed in digital preservation? Perhaps a brief intro document that links readers who require more information to resources with more in-depth coverage of a specific term. At least add a sentence to briefly define each PREMIS and TRAC, especially PREMIS because we lean on it as a definition up front. The intro information could link off to the Levels of Preservation, and other resources. There should be some language addressing how the data to be preserved was created and workflow information, and something on the kind of data you should keep about your fixity check like the tools you used, when the data was checked, the results, and what algorithm used. Where will this document live, and what is this document, e.g., a factsheet or a guidance document? Trevor will refer to a grey literature guide to recommend what call the document, update it, and distribute to a larger group to solicit feedback and broader input.

	~~Bill~~ and Karen tried to pull together a summary of the four talks, ~~but they were all very different~~. Islandora, Hydra, Archivematica and Open Planets. There were some themes, open source as an ecosystem. staffing and open source platforms~~. Does anyone want to jump in and help, or should they start over~~. The goal was to ~~pull the presentations together and report out~~ what the working group learned. The workng group decided they wanted to have these themed presentations together. Because their were blog posts on The Signal, they have been reported out. There was an attempt to pull out some cross-cutting themes, though. Trevor, Chelcie, Joe and Karen will attempt to work on this, and share via Google Doc before they bring it back to the larger group.		Joe and Karen tried to pull together a summary of the four talks, i.e., Islandora, Hydra, Archivematica and Open Planets, but they were all very different. There were some themes, e.g., open source as an ecosystem and the intersection of staffing and open source platforms. The goal was to publish a blog post on what the working group learned, and bring the presentations together more thematically. The workng group decided they wanted to have these themed presentations together. Because their were blog posts on The Signal, they have been reported out. There was an attempt to pull out some cross-cutting themes, though. Trevor, Chelcie, Joe and Karen will attempt to work on this, and share via Google Doc before they bring it back to the larger group.

	We've been chasing down a few stray respondants, but in the near future we'll have something to share with the greater group.		We've been chasing down a few stray respondants, but in the near future we'll have something to share with the greater group.
Line 38:		Line 38:
	The Coordinating Committee has requested the working groups begin discussing the update to the National Agenda. Any infrastructure issues that should be elevated to the national level. IA and Olive Library have launched emulation environments. Take it from the research phase to implementation phase. Funding on a national level, and metrics on what it takes for forward migration within specific storage environments. What about when you change formats?		The Coordinating Committee has requested the working groups begin discussing the update to the National Agenda. Any infrastructure issues that should be elevated to the national level. IA and Olive Library have launched emulation environments. Take it from the research phase to implementation phase. Funding on a national level, and metrics on what it takes for forward migration within specific storage environments. What about when you change formats?

	2) ~~Pull themes that came out of the conversations. Blog post that links the themes together more thematically.~~ Work on a google doc trying to highlight the themes and use the conversation as highlights and examples. Karen, Joe, Trevor -Chelsea has also offered to help.		2) Work on a google doc trying to highlight the themes and use the conversation as highlights and examples. Karen, Joe, Trevor -Chelsea has also offered to help.

	3) NDSA storage survey update –		3) NDSA storage survey update –