NDSA:Tuesday, January 31, 2012 - Revision history

Dlfadm: 1 revision imported: Migrate NDSA content from Library of Congress

2016-02-11T19:19:19Z

1 revision imported: Migrate NDSA content from Library of Congress

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

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

2016-02-11T19:19:07Z

6 revisions imported: Migrate NDSA content from Library of Congress

@@ Line 1: / Line 1: @@
-On the content group item:
+Infrastructure Working Group Call, January 31, 2012, 2pm-3pm
-I was looking through CC stuff, and found these CC plugins for wordpress, which may be of interest to the content group's initiative to enable easy opt-in to preservation:
+*Trevor Owens, Library of Congress
-http://code.creativecommons.org/viewgit/wordpress-cc-plugin.git/
+==Agenda==
-This was from a CC-lead GSOC effort in 2010.
+==Storage Report==
-Also, there seem to be a number of other plugins extant in that space:
+==OSS Project==
-http://www.g-loaded.eu/2006/01/14/creative-commons-configurator-wordpress-plugin/
+==Other NDSA news==
-http://wordpress.org/extend/plugins/creative-commons-license-widget/
-http://wordpress.org/extend/plugins/wplicense/
+==Innovation news==
-http://wordpress.org/extend/plugins/creative-commons-suite/
+* Innovation members are planning on participating in the Google Summer of Code project. If any Infrastructure members would like to take part (which involves mentoring a student developer/programmer who will write code for an open-source software project), contact Jefferson or Trevor and we will provide more info on the project & requirements.

Micah altman: Created page with 'On the content group item: I was looking through CC stuff, and found these CC plugins for wordpress, which may be of interest to the content group's initiative to enable easy o…'

2012-02-28T14:59:15Z

Created page with 'On the content group item: I was looking through CC stuff, and found these CC plugins for wordpress, which may be of interest to the content group's initiative to enable easy o…'

@@ Line 1: / Line 1: @@
-Infrastructure Working Group Call, January 31, 2012, 2pm-3pm
+On the content group item:
-*Trevor Owens, Library of Congress
+I was looking through CC stuff, and found these CC plugins for wordpress, which may be of interest to the content group's initiative to enable easy opt-in to preservation:
-==Agenda==
+http://code.creativecommons.org/viewgit/wordpress-cc-plugin.git/
-==Storage Report==
+This was from a CC-lead GSOC effort in 2010.
-==OSS Project==
+Also, there seem to be a number of other plugins extant in that space:
-==Other NDSA news==
+http://www.g-loaded.eu/2006/01/14/creative-commons-configurator-wordpress-plugin/
+http://wordpress.org/extend/plugins/creative-commons-license-widget/
-==Innovation news==
+http://wordpress.org/extend/plugins/wplicense/
-* Innovation members are planning on participating in the Google Summer of Code project. If any Infrastructure members would like to take part (which involves mentoring a student developer/programmer who will write code for an open-source software project), contact Jefferson or Trevor and we will provide more info on the project & requirements.
+http://wordpress.org/extend/plugins/creative-commons-suite/

Nicho147: /* Attending */

2012-02-02T21:21:28Z

Attending

← Older revision		Revision as of 17:21, 2 February 2012
Line 23:		Line 23:
	*Andrea Goethels, Harvard University		*Andrea Goethels, Harvard University
	*Linda Tadic, Audiovisual Archive Network		*Linda Tadic, Audiovisual Archive Network
	*~~Shaun~~ Nicholson, Michigan State		*Shawn Nicholson, Michigan State
	*Martin Halbert, UNT		*Martin Halbert, UNT

Karen cariani at 14:09, 1 February 2012

2012-02-01T14:09:37Z

← Older revision		Revision as of 10:09, 1 February 2012
Line 42:		Line 42:
	*We are continuing to brainstorm on potential questions and who exactly to pose them to as far as decision-making around open-source software use for digital preservation.		*We are continuing to brainstorm on potential questions and who exactly to pose them to as far as decision-making around open-source software use for digital preservation.
	*There is still a lack of clarity on who we want to invite to comment and how we proceed developing question.		*There is still a lack of clarity on who we want to invite to comment and how we proceed developing question.
	*One ~~ideas~~ is to develop questions for ourselves first (meaning the working group), then refine the question, then post to the NDSA membership (much like the storage survey).		*One idea is to develop questions for ourselves first (meaning the working group), then refine the question, then post to the NDSA membership (much like the storage survey).
	*Would also be useful to talk to folks who are experts or have experience in this area to tease out issues before writing questions.		*Would also be useful to talk to folks who are experts or have experience in this area to tease out issues before writing questions.
	*Are our questions around decision-making for using, or for participating in and contributing to projects?		*Are our questions around decision-making for using, or for participating in and contributing to projects?

Jbailey: /* OSS Project */

2012-02-01T13:38:01Z

OSS Project

← Older revision		Revision as of 09:38, 1 February 2012
Line 48:		Line 48:
	*We need to figure out the scope of the questions -- should we make distinctions between types of software (there’s a difference between file-renaming software and a full repository) – what’s our focus?		*We need to figure out the scope of the questions -- should we make distinctions between types of software (there’s a difference between file-renaming software and a full repository) – what’s our focus?
	*One use-case: enterprise tools for long-term access/preservation. That is a decision that involves a different time horizon (for long-term preservation in memory institutions) than a commercial, enterprise-wide solution.		*One use-case: enterprise tools for long-term access/preservation. That is a decision that involves a different time horizon (for long-term preservation in memory institutions) than a commercial, enterprise-wide solution.
	*Also the case of OSS on top of commercial piece (combination of ~~built~~, buy, and adopt).		*Also the case of OSS on top of commercial piece (combination of build, buy, and adopt).
	*Also the case of “commercial open source” which is increasingly prevalent, underlying OSS but with pay-for features or support or implementation on top of it.		*Also the case of “commercial open source” which is increasingly prevalent, underlying OSS but with pay-for features or support or implementation on top of it.
	*It would work best to hone the focus before we begin thinking of questions and/or communities/institutions to query.		*It would work best to hone the focus before we begin thinking of questions and/or communities/institutions to query.

Jbailey: /* OSS Project */

2012-02-01T13:37:37Z

OSS Project

← Older revision		Revision as of 09:37, 1 February 2012
Line 48:		Line 48:
	*We need to figure out the scope of the questions -- should we make distinctions between types of software (there’s a difference between file-renaming software and a full repository) – what’s our focus?		*We need to figure out the scope of the questions -- should we make distinctions between types of software (there’s a difference between file-renaming software and a full repository) – what’s our focus?
	*One use-case: enterprise tools for long-term access/preservation. That is a decision that involves a different time horizon (for long-term preservation in memory institutions) than a commercial, enterprise-wide solution.		*One use-case: enterprise tools for long-term access/preservation. That is a decision that involves a different time horizon (for long-term preservation in memory institutions) than a commercial, enterprise-wide solution.
	*Also the case of OSS on top of commercial piece (combination of built~~-by~~ and adopt).		*Also the case of OSS on top of commercial piece (combination of built, buy, and adopt).
	*Also the case of “commercial open source” which is increasingly prevalent, underlying OSS but with pay-for features or support or implementation on top of it.		*Also the case of “commercial open source” which is increasingly prevalent, underlying OSS but with pay-for features or support or implementation on top of it.
	*It would work best to hone the focus before we begin thinking of questions and/or communities/institutions to query.		*It would work best to hone the focus before we begin thinking of questions and/or communities/institutions to query.

Jbailey at 13:33, 1 February 2012

2012-02-01T13:33:30Z

← Older revision		Revision as of 09:33, 1 February 2012
Line 3:		Line 3:
	==Attending==		==Attending==

	Trevor Owens, Library of Congress		*Trevor Owens, Library of Congress
	Karen Cariani, WGBH		*Karen Cariani, WGBH
	Dave MacCarn, WGBH		*Dave MacCarn, WGBH
	Jefferson Bailey, Library of Congress		*Jefferson Bailey, Library of Congress
	Aaron Trehub, Auburn University		*Aaron Trehub, Auburn University
	Mitch Brodsky, NY Philharmonic		*Mitch Brodsky, NY Philharmonic
	John Spenser, BMS Chase		*John Spenser, BMS Chase
	Martin Jacobson, NARA		*Martin Jacobson, NARA
	Michael Sterling, Academy of Motion Pictures		*Michael Sterling, Academy of Motion Pictures
	Corey Snavely, University of Michigan		*Corey Snavely, University of Michigan
	Micah Altman, Harvard University (soon to be MIT)		*Micah Altman, Harvard University (soon to be MIT)
	Nicole Scalessa, Library Company of Philadelphia		*Nicole Scalessa, Library Company of Philadelphia
	Dean Farrell, UNC		*Dean Farrell, UNC
	Elizabeth Perkes, Utah State Archives		*Elizabeth Perkes, Utah State Archives
	Bob Downs, Columbia University		*Bob Downs, Columbia University
	Joe Pawletko, NYU		*Joe Pawletko, NYU
	Dan Dodge, Thompson Reuters		*Dan Dodge, Thompson Reuters
	Priscilla Caplan, FCLA		*Priscilla Caplan, FCLA
	Andrea Goethels, Harvard University		*Andrea Goethels, Harvard University
	Linda Tadic, Audiovisual Archive Network		*Linda Tadic, Audiovisual Archive Network
	Shaun Nicholson, Michigan State		*Shaun Nicholson, Michigan State
	Martin Halbert, UNT		*Martin Halbert, UNT

	==Agenda==		==Agenda==

Jbailey: Created page with 'Infrastructure Working Group Call, January 31, 2012, 2pm-3pm ==Attending== Trevor Owens, Library of Congress Karen Cariani, WGBH Dave MacCarn, WGBH Jefferson Bailey, Library of…'

2012-02-01T13:32:53Z

Created page with 'Infrastructure Working Group Call, January 31, 2012, 2pm-3pm ==Attending== Trevor Owens, Library of Congress Karen Cariani, WGBH Dave MacCarn, WGBH Jefferson Bailey, Library of…'

New page

Infrastructure Working Group Call, January 31, 2012, 2pm-3pm

==Attending==

Trevor Owens, Library of Congress
Karen Cariani, WGBH
Dave MacCarn, WGBH
Jefferson Bailey, Library of Congress
Aaron Trehub, Auburn University
Mitch Brodsky, NY Philharmonic
John Spenser, BMS Chase
Martin Jacobson, NARA
Michael Sterling, Academy of Motion Pictures
Corey Snavely, University of Michigan
Micah Altman, Harvard University (soon to be MIT)
Nicole Scalessa, Library Company of Philadelphia
Dean Farrell, UNC
Elizabeth Perkes, Utah State Archives
Bob Downs, Columbia University
Joe Pawletko, NYU
Dan Dodge, Thompson Reuters
Priscilla Caplan, FCLA
Andrea Goethels, Harvard University
Linda Tadic, Audiovisual Archive Network
Shaun Nicholson, Michigan State
Martin Halbert, UNT

==Agenda==
*Update on Storage Report activities
*Discussion of our OSS project
*Update on other NDSA WG activities

==Storage Report==
*Two posts have been published on the NDIIPP blog highlighting and analyzing results from the NDSA storage survey.
*Access: http://blogs.loc.gov/digitalpreservation/2011/12/diversity-of-access-to-digital-preservation-collections-first-results-from-the-ndsa-storage-survey/
*Cloud: http://blogs.loc.gov/digitalpreservation/2012/01/partly-cloudy-trends-in-distributed-and-remote-preservation-storage-more-results-from-the-ndsa-storage-survey/
*Three more are planned: one (in draft form now) on fixity, one on administrative/managerial complexities, and one summary post that can also included any stats/results that didn’t fall into the previous four posts.
*We are still tossing around ideas for the form of a final product from this project, so ping the list if you have ideas or would like to be involved in that effort.

==OSS Project==
Discussion:
*We are continuing to brainstorm on potential questions and who exactly to pose them to as far as decision-making around open-source software use for digital preservation.
*There is still a lack of clarity on who we want to invite to comment and how we proceed developing question.
*One ideas is to develop questions for ourselves first (meaning the working group), then refine the question, then post to the NDSA membership (much like the storage survey).
*Would also be useful to talk to folks who are experts or have experience in this area to tease out issues before writing questions.
*Are our questions around decision-making for using, or for participating in and contributing to projects?
*One potential approach is to look at thinks like Lyasis’ FLOSS project and other the other resources on the wiki. Then we can comment on what features or formats we like from those materials materials.
*We need to figure out the scope of the questions -- should we make distinctions between types of software (there’s a difference between file-renaming software and a full repository) – what’s our focus?
*One use-case: enterprise tools for long-term access/preservation. That is a decision that involves a different time horizon (for long-term preservation in memory institutions) than a commercial, enterprise-wide solution.
*Also the case of OSS on top of commercial piece (combination of built-by and adopt).
*Also the case of “commercial open source” which is increasingly prevalent, underlying OSS but with pay-for features or support or implementation on top of it.
*It would work best to hone the focus before we begin thinking of questions and/or communities/institutions to query.

==Other NDSA news==

==Innovation news==
* Innovation members are planning on participating in the Google Summer of Code project. If any Infrastructure members would like to take part (which involves mentoring a student developer/programmer who will write code for an open-source software project), contact Jefferson or Trevor and we will provide more info on the project & requirements.
*Innovation Awards: the annual awards program will be announced soon and more information will be disseminated NDSA-wide. Please make, and encourage others to make, nominations for people, projects, institutions, or students/educators demonstrating innovation in the field of digital preservation and stewardship.

==Standards==
*There is a “wiki project” in development to document digital preservation standards and guidelines on Wikipedia
*Another project is to conduct a staffing survey to see how institutions have staffed themselves for digital preservation: numbers of employees, organizational structure, skills expected of employees/job applications, their ideal staffing levels, their projected staffing levels, etc. The survey will be of both the NDSA community and external institutions
*Another project is to conduct a survey of what standards are currently in use around digital preservation tasks at NDSA institution and then track this information over time to determine trends, etc.

==Outreach==
*Creating “digital preservation in a box” a collection of resources for digital preservation
*Storytellers series, which collects unique or evocative stories about digital preservation

==Content==
*Working with WordPress to develop an “opt-in” plug-in which blog creators can activate to note their content is available/allowable for harvesting.

==Action items==
*Trevor/Micah will write a short, one paragraph statement scoping out a baseline description for considering OSS when building digital preservation infrastructure for long-term access & preservation.
*The group will review text posted to the wiki and comment over the listserv.
*The group will continue reviewing, commenting on, and adding to the OSS resources currently posted to the wiki, especially anything that provides a good example or model of what we hope to provide.
*Related: The Digital Dilemma 2 paper is now available for download
*Next call will be Tuesday, February 28, 2012 at 2pm EST