<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Open House Project &#187; preservation</title>
	<atom:link href="http://www.theopenhouseproject.com/category/preservation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theopenhouseproject.com</link>
	<description>Recommendations, Resources, and Reform</description>
	<lastBuildDate>Fri, 03 Sep 2010 15:39:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Transparency in Healthcare and Scientific Research</title>
		<link>http://www.theopenhouseproject.com/2008/02/12/transparency-in-healthcare-and-scientific-research/</link>
		<comments>http://www.theopenhouseproject.com/2008/02/12/transparency-in-healthcare-and-scientific-research/#comments</comments>
		<pubDate>Tue, 12 Feb 2008 18:08:06 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[harvard]]></category>
		<category><![CDATA[legal research]]></category>
		<category><![CDATA[nih]]></category>
		<category><![CDATA[nsf]]></category>
		<category><![CDATA[preservation]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/02/12/transparency-in-healthcare-and-scientific-research/</guid>
		<description><![CDATA[As the research of the Harvard Transparency Policy Project has made abundantly clear, applying the principles of openness and transparency to complex systems demands a careful approach to epistemic nuances; questions like what should be knowable to whom need to be answered before disclosure requirements are implemented, and need to be built into a disclosure [...]]]></description>
			<content:encoded><![CDATA[<p>As the research of the <a id="e-18" title="Harvard Transparency Policy Project" href="http://www.ksg.harvard.edu/taubmancenter/transparency/papers.htm">Harvard Transparency Policy Project</a> has <a id="sj8o" title="made" href="http://www.theopenhouseproject.com/2007/12/05/transparency-via-gao-academia/">made</a> abundantly clear, applying the principles of openness and transparency to complex systems demands a careful approach to epistemic nuances; questions like what should be knowable to whom need to be answered before disclosure requirements are implemented, and need to be built into a disclosure regime&#8217;s initial design.</p>
<p>It looks like the <a id="rpwr" title="Committee for Economic Development" href="http://www.ced.org/">Committee for Economic Development</a>, a DC public policy NGO, has undertaken a systematic study of openness as it applies to American Health Care.Ã‚Â  Their new report (<a id="j9y5" title="pdf" href="http://www.ced.org/docs/report/report_healthcare2007dcc.pdf">pdf</a>), &#8220;Harnessing Openness to Transform American Health Care&#8221;, examines healthcare&#8217;s potential transformation in the face of Internet technology, much like the Open House Project has for Congress: &#8220;Our goal in this report is to bring the DCC&#8217;s expertise in information and communications technology and electronic commerce to bear on those aspects of healthcare that have been or can be changed by the Internet, the continued growth in computing power and data storage capacity, and the increasing digitization of information.Ã‚Â  These technological changes, and the greater openness that they enable, are visible in areas that range from biomedical research and the disclosure of research findings, through the process of evaluating drugs and devices, to the emergence of electronic health records, and the development and implementation of treatment regimes by caregivers and patients.&#8221;Ã‚Â  (<a id="nb:c" title="pdf" href="http://www.ced.org/docs/report/report_healthcare2007dcc.pdf">pdf</a>, page 1)</p>
<p>This is absolutely a step in the right direction, and I&#8217;m glad to see a concerted well coordinated analysis of disclosure in other fields.Ã‚Â  This study pairs nicely with the <a id="ri0m" title="recently passed requirement" href="http://www.govtrack.us/congress/bill.xpd?bill=s110-1710">recently passed requirement</a> that the National Institutes of Health <a id="j46b" title="disclose results" href="http://publicaccess.nih.gov/">disclose results</a> of publicly funded research.Ã‚Â  (I&#8217;m not sure which bill is responsible for this reform, if you are, let us know in the comments.)</p>
<p>If you look through the National Science Foundation&#8217;s <a id="zchs" title="requests for proposals" href="http://www.nsf.gov/funding/pgm_list.jsp?org=OCI">requests for proposals</a>, many of them pertain to the cyber-infrastructure issues that are the stuff of the future of public science collaboration.Ã‚Â  I&#8217;m especially fond of theÃ‚Â  <span class="pageheadline">&#8220;Sustainable Digital Data Preservation and Access Network PartnersÃ‚Â (DataNet)&#8221; <a id="xf1v" title="rfp" href="http://www.nsf.gov/funding/pgm_summ.jsp?pims_id=503141&#038;org=OCI&#038;sel_org=OCI&#038;from=fund">rfp</a></span>, because my <a href="http://www.flickr.com/photos/johnarthurw/2115252517/">sister researches HIV</a>, and I&#8217;ve witnessed the contorted amalgamation of web searches scientific researchers need to go through to stay on top of their field.Ã‚Â  Scientific discoveries and health information both face the same public access revolution that legislative information does, and I&#8217;m happy to see when the problems are being approached in the same public, collaborative manner.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/02/12/transparency-in-healthcare-and-scientific-research/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>GAO Document on Electronic Dissemination of Government Publications</title>
		<link>http://www.theopenhouseproject.com/2008/01/31/gao-document-on-electronic-dissemination-of-government-publications/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/31/gao-document-on-electronic-dissemination-of-government-publications/#comments</comments>
		<pubDate>Thu, 31 Jan 2008 21:34:40 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[FDLP]]></category>
		<category><![CDATA[GAO]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[archivist]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[preservation]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/31/gao-document-on-electronic-dissemination-of-government-publications/</guid>
		<description><![CDATA[In 2001, the GAO published a document entitled &#8220;Information Management; Electronic Dissemination of Government Publications&#8221; (pdf).
The GAO is responding to a congressional request for information on electronic documents dissemination, and ends up discussing the GPO, LOC, and FDLP in great detail.  Apparently they considered transferring the FDLP from the GPO to the LOC.
Also, the [...]]]></description>
			<content:encoded><![CDATA[<p>In 2001, the GAO published a document entitled &#8220;Information Management; Electronic Dissemination of Government Publications&#8221; (<a href="http://www.gao.gov/new.items/d01428.pdf">pdf</a>).</p>
<p>The GAO is responding to a congressional request for information on electronic documents dissemination, and ends up discussing the GPO, LOC, and FDLP in great detail.  Apparently they considered transferring the FDLP from the GPO to the LOC.</p>
<p>Also, the report lists the essential documents which must continue to be printed, regardless of how digitized we become.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/31/gao-document-on-electronic-dissemination-of-government-publications/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reading Notes on The Documentation of Congress</title>
		<link>http://www.theopenhouseproject.com/2008/01/27/reading-notes-on-the-documentation-of-congress/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/27/reading-notes-on-the-documentation-of-congress/#comments</comments>
		<pubDate>Sun, 27 Jan 2008 22:45:23 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[CLA]]></category>
		<category><![CDATA[Member Web Sites]]></category>
		<category><![CDATA[NARA]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[jurisdiction]]></category>
		<category><![CDATA[legal research]]></category>
		<category><![CDATA[library of congress]]></category>
		<category><![CDATA[lobbying]]></category>
		<category><![CDATA[lobbying disclosure]]></category>
		<category><![CDATA[ota]]></category>
		<category><![CDATA[preservation]]></category>
		<category><![CDATA[senate]]></category>
		<category><![CDATA[spub 102-20]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/27/reading-notes-on-the-documentation-of-congress/</guid>
		<description><![CDATA[After going through the trouble of obtaining and digitizing the 1992 report on congressional documentation, I&#8217;ve started going systematically through the document, and, in an attempt to read more closely, have been taking notes.Ã‚Â  This is a long post, but the parallels with the Open House Project are startling to me, as are the contrasts: [...]]]></description>
			<content:encoded><![CDATA[<p>After going through the trouble of obtaining and digitizing the 1992 report on congressional documentation, I&#8217;ve started going systematically through the document, and, in an attempt to read more closely, have been taking notes.Ã‚Â  This is a long post, but the parallels with the Open House Project are startling to me, as are the contrasts: since 1992 the consumer of public information has undergone a fundamental transformation, leading what was once considered relevant for archivists or researchers to become essential to practitioners of a new online breed of civic engagement.</p>
<p>For more background on the document, see <a href="http://www.theopenhouseproject.com/2007/12/19/spub-102-20/">this post</a>, and for updates, I&#8217;m keeping notes on <a href="http://docs.google.com/Doc?id=ddj3rw4t_2276k773kfc">this page</a>, from which future updates will likely be pulled.</p>
<p>-JohnÃ‚Â  (start review)</p>
<p><span id="more-242"></span></p>
<p>foreword:<br />
compiled by the Task Force on the Documentation of Congress of the Society of American Archivists Congressional Archivists Roundtable, coming from 1989&#8217;s &#8220;Understanding Congress: A Bicentennial Research Conference&#8221;.Ã‚Â  &#8220;the fragmented nature of congressional primary source documentation&#8221; is partly responsible for the lack of scholarly writing on the legislative branch.Ã‚Â  Report is a &#8220;study of the archival sources that document the operations of Congress.&#8221;</p>
<p>Preface:<br />
&#8220;Because the documentation of Congress, in particular, most directly reveals the will of the people as expressed through their elected representatives, it is especially crucial to preserve evidence and information about the legislative process and make it accessible to the public.&#8221;Ã‚Â  (gives great detail on problems with public access: &#8220;fragmented and geographically scattered; collections are often voluminous, of complex arrangement, inadequately indexed, and in poor physical condition; contents of many collections are uneven, with unexplained gaps in information; and repositories that receive these collections frequently lack the resources to provide state-of-the-art arrangement, description, and archival preservation.&#8221;Ã‚Â  Project undertaken by the Task Force on Congressional Documentation of the Society of American Archivists&#8217; Congressional Archivists Roundtable (that&#8217;s correctly transcribed).Ã‚Â  &#8220;many of its suggestions will take years to be carried out; others can be effected immediately.&#8221;Ã‚Â  &#8220;Among the most pressing needs are actions to improve the documentation of legislation, representation, congressional leadership, political activities, and programs of congressional support agencies.Ã‚Â  Other recommendations are aimed at better documenting Congress&#8217; relations and interaction with media, the executive and the judicial branches, lobbyists, and think tanks.Ã‚Â  Finally, steps are suggested to improve documentation of the administration of Congress&#8217; to fill gaps in the historical record through structured, coordinated oral history interview programs; and to improve the preservation of congressional sources.</p>
<p>Intro:<br />
Report organized into congressional &#8220;functions&#8221;, &#8220;documentation&#8221;, and &#8220;recommendations&#8221;.Ã‚Â  (apparently there&#8217;s a 1978 report from the National Study Commission on the Records and Documents of Federal Officials, which &#8220;recommended that office files and personal papers of members of Congress be legally designated as federal records with guaranteed public access after fifteen years&#8221; (this wasn&#8217;t implemented, but that report would be useful to find).Ã‚Â  This report led to a 2 day conference, where they decided to publish a handbook on member records management.Ã‚Â  1985 then saw a 2 day conference on documenting Congress, put on by the &#8220;Dirksen Congressional Center and the national Historical Publications and Records Commission&#8221; (another great report to find)Ã‚Â  This conference led to the creation of the Congressional Archivists Roundtable of the Society of American Archivists (which, in turn, led to the current day 2008 Advisory Committee on the Records of Congress (<a id="u05t" title="link" href="http://www.archives.gov/legislative/cla/advisory-committee/">link</a>).Ã‚Â  (The Congressional Archivists Roundtable appears to be defunct, perhaps being defunded in the mid 90&#8217;s?)Ã‚Â  &#8220;the &#8220;importance&#8221; [of congressional material] had not led to a determined effort to systematically appraise and preserve a documentary record of Congress.&#8221; (page vi)Ã‚Â  Problems archivists face: &#8220;the information explosion, the computer and telecommunications revolutions, insufficient resources for archival work as government and repository budgets tighten, and the lack of clearly defined long-term strategies and action plans to accomplish overall documentary objectives.&#8221;Ã‚Â  The response to this is a strategy, which matches the organization of this document (functions, documentation, and recommendations).Ã‚Â Ã‚Â Ã‚Â  The report then lists participants.</p>
<p>Page ix lists contents, listing the major topics to be examined: Institutional Setting, the Legislative Process, Representation, Political Activities, External Relations, Administration and Support, Research Use of Congressional Collections, Appendices, and Notes.</p>
<p>Summary Report and Recommendations<br />
Repeats problem.Ã‚Â  &#8220;Historical records do not simply materialize.&#8221;Ã‚Â  They&#8217;re trying to balance the needs of three authorities: members and officials of Congress &#8220;individually responsible for the on-site management of the information that is collected and maintained in their offices&#8221;, NARA&#8217;s CLA, and the &#8220;literally hundreds of archival repositories across the country [that] preserve and provide access to the personal papers that are deposited in them by the members&#8221;.Ã‚Â  This listing seems to me to be a result of their institutional setting, my take on the jurisdictions at work in congressional information access can be found <a id="g9b0" title="here" href="http://www.theopenhouseproject.com/2008/01/23/governmental-support-entities-with-a-role-in-transparency-statutory-basis-for-negotiated-terrain/">here</a>.</p>
<p>Major Findings:<br />
1. &#8220;Congressional committees are relatively, although not uniformly, well documented, [but] there is great variation in the documentary quality of individual members&#8217; collections&#8221;Ã‚Â  This conclusion strikes me as a result of writing in the mid 1990s, when paying meaningful attention to legislative affairs through the Internet was rather impossible.Ã‚Â  There was little difference then between &#8220;well documented&#8221; and &#8220;publicly available (online)&#8221;, where now that difference is quite clear.Ã‚Â  What is &#8220;well documented&#8221;, like committee hearing transcripts, or the upcoming schedules for committee hearings, in the archival sense, can also be useless for those hoping to actually watch Congress in action, even in time for upcoming elections, which is a much lower bar than the near-real time awareness lobbyists need in order to be legislatively relevant.Ã‚Â  Thus the report&#8217;s focus on member records, which were managed in a much less standard manner then.</p>
<p>2. The need for a &#8220;coordinated retention plan that meets the long-term needs of Congress&#8221; as applied to congressional support agencies.Ã‚Â  The GAO was doing well, the (now defunct) Office of Technology Assessment and Government Printing Office had partial programs, and the CRS and CBO had none.Ã‚Â  Again, no real mention of OTA and GAO providing public documentation while CRS does not.Ã‚Â  Our expectations of finding things online has led to a new set of expectations.Ã‚Â  (well, that and the expectation of equal access to publicly funded documents, since CRS reports are sold through private companies.)</p>
<p>3. Executive Branch and Judicial Branches are doing a rather good job, but are relevant here nevertheless.</p>
<p>4. Other sources they feel have been thitherto overlooked: nat&#8217;l, congressional, and individual campaign committees, political party organizations; and congressional member organizations and caucuses.Ã‚Â  (still true, 16 years later)</p>
<p>5. Member documentary repositories are hard to use, recommend better practices here.</p>
<p>6. Member materials will be better processed if offices hire and train archivists, and keep up with documents processing.</p>
<p>The Report then launches into specific recommendations, lining up with the table of contents, but in summary form.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/27/reading-notes-on-the-documentation-of-congress/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>FDsys, GPO&#8217;s vision, FDLP</title>
		<link>http://www.theopenhouseproject.com/2008/01/11/fdsys-gpos-vision-fdlp/</link>
		<comments>http://www.theopenhouseproject.com/2008/01/11/fdsys-gpos-vision-fdlp/#comments</comments>
		<pubDate>Fri, 11 Jan 2008 20:59:05 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[GPO]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[archivist]]></category>
		<category><![CDATA[preservation]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2008/01/11/fdsys-gpos-vision-fdlp/</guid>
		<description><![CDATA[Is anyone familiar with FDsys being developed by the GPO?  From the website:
The Office of the Chief Information Officer is working to develop GPO&#8217;s Digital Information System (FDsys). As outlined in the Strategic Vision, FDsys will allow federal agencies to easily create and submit content that can then be preserved, authenticated, managed and delivered [...]]]></description>
			<content:encoded><![CDATA[<p>Is anyone familiar with FDsys being developed by the GPO?  From the <a target="_blank" href="http://www.gpo.gov/projects/fdsys_overview.htm">website</a>:</p>
<div style="margin-left: 40px">The Office of the Chief Information Officer is working to develop GPO&#8217;s Digital Information System (FDsys). As outlined in the Strategic Vision, FDsys will allow federal agencies to easily create and submit content that can then be preserved, authenticated, managed and delivered upon request. FDsys will form the core of GPO&#8217;s future operations.FDsys will include all known Federal Government documents within the scope of GPO&#8217;s <strong>Federal Depository Library Program (FDLP)</strong>, whether printed or electronic. Information entered into the system will be authenticated and catalogued according to GPO metadata and document creation standards. Content will include text, graphics, audio, and video files. It will be available for online searching and viewing, downloading and printing, and as document masters for conventional and on-demand printing.FDsys is being developed in phases and currently included three scheduled releases. The first public release is scheduled for 2008.</div>
<p>The <a target="_blank" href="http://www.gpo.gov/projects/fdsys_status.htm">status page</a> has a fascinating run through the project&#8217;s expected development, including user profiles, file conversion, customizable alerts, and even a &#8220;collaborative working environment&#8221;.  I wonder if this is directed towards the work of GPO, or towards the creation of government-wide documents that end up archived by the FDLP?<br />
The GPO&#8217;s mission statement lists 3 main functions: (quoting)</p>
<p style="margin-left: 40px">&#8220;To provide the agencies and organizations which make up the three branches of the Federal government with expert publishing and printing services, on a cost recovery basis&#8230; To provide, in partnership with Federal Depository libraries, for nationwide community facilities for the perpetual, free and ready access to the printed and electronic documents&#8230;  To distribute, on a cost recovery basis, copies of printed and electronic documents&#8230;to the general public.&#8221;<br />
I wonder to what degree this is coordinated or overlaps with the functions of OMB or the GSA?  (this may be another example of negotiated terrain.)The <a target="_blank" href="http://www.gpo.gov/congressional/pdfs/04strategicplan.pdf"> strategic vision</a> suggests that the &#8220;digital information system&#8221; will &#8220;[catalogue and authenticate] all known Federal Government documents within the scope of FDLP, whether printed or born digital.&#8221; ( p.4)</p>
<p>This reworking of the FDLP may require new authorization, as envisioned, as page 9 says &#8220;GPO will also ask Congress to review proposed changes to the FDLP to determine whether or not new legislative authority is required.&#8221;</p>
<p>I also wonder about overlap between the new GPO envisioned FDLP and NARA, although I guess that depends on FDLP and NARA&#8217;s guidelines on what they preserve and maintain access to.  The GPO vision also suggests the creation of &#8220;two collections, on in the East and one in teh West, which will hold all known tangible and electronic FDLP documents withdrawn on a controlled basis as a last resort when no circulating copy is available.&#8221;  Is this a departure from the LOCKSS model of preservation (Lots Of Copies Keep Stuff Safe) and model of FDLP function outlined in FGInfo&#8217;s  <a href="http://3stages.org/jj/w/fdlp/">report</a> Once and Future Federal Depository Library Program?</p>
<p>I don&#8217;t know.  But there&#8217;s a lot of information about coordinating resources and understanding government agencies&#8217; jurisdiction to process here.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2008/01/11/fdsys-gpos-vision-fdlp/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Web Harvest Archive</title>
		<link>http://www.theopenhouseproject.com/2007/12/04/web-harvest-archive/</link>
		<comments>http://www.theopenhouseproject.com/2007/12/04/web-harvest-archive/#comments</comments>
		<pubDate>Tue, 04 Dec 2007 16:58:16 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[CLA]]></category>
		<category><![CDATA[Congress]]></category>
		<category><![CDATA[NARA]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[archivist]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[preservation]]></category>
		<category><![CDATA[sitemap protocol]]></category>
		<category><![CDATA[sitemapping]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/12/04/web-harvest-archive/</guid>
		<description><![CDATA[I&#8217;m glad to have just found the archive of old Web sites from members of Congress, maintained by the Center for Legislative Archives under the National Archives and Records Administration (NARA).
The collection seems well organized and easy to peruse, with solid explanations of their methodology and disclaimers about what&#8217;s available based on the crawling.
My main [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m glad to have just found the <a title="archive of old Web sites" id="e1od" href="http://www.webharvest.gov/collections/">archive of old Web sites</a> from members of Congress, maintained by the <a title="Center for Legislative Archives" id="dugl" href="http://www.google.com/url?sa=t&#038;ct=res&#038;cd=1&#038;url=http%3A%2F%2Fwww.archives.gov%2Flegislative%2F&#038;ei=_YVVR9HQBoX8gAS0tKnyCA&#038;usg=AFQjCNEzLtvCA2NtPrVmqTpY4kDzbg5oNw&#038;sig2=89L1QgDMUonK8VSoLQOmyQ">Center for Legislative Archives</a> under the National Archives and Records Administration (NARA).</p>
<p>The collection seems well organized and easy to peruse, with solid explanations of their methodology and disclaimers about what&#8217;s available based on the crawling.</p>
<p>My main suggestion is that the archiving happen with greater frequency, perhaps coordinated in order to capture the greatest amount of material possible, and for those responsible for the Web Harvest to coordinate with the CAO, systems administrators, and vendors to be sure that the digital records management practices used in organizing member sites encourages easy crawling and archiving by NARA and CLA.</p>
<p>The House has a document laying out best practices for documents management for House offices; I wonder if the digital materials management should be expanded to include digital materials availability, perhaps including standards like <a title="sitemapping" id="f5e_" href="http://googlepublicpolicy.blogspot.com/2007/11/senate-helping-make-govt-more.html">sitemapping</a>, in order to ensure the preservation of member sites?</p>
<p>My other suggestion is to increase the exposure of the captured sites, perhaps encouraging links from the <a title="bioguides" id="gkt1" href="http://bioguide.congress.gov/biosearch/biosearch.asp">bioguides</a>, or current member sites, and to ensure that the collection itself is crawlable through search engine indexing <a title="practices" id="frdt" href="http://googlepublicpolicy.blogspot.com/2007/11/senate-helping-make-govt-more.html">practices</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/12/04/web-harvest-archive/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NARA Looking for Public Input</title>
		<link>http://www.theopenhouseproject.com/2007/09/10/nara-looking-for-public-input/</link>
		<comments>http://www.theopenhouseproject.com/2007/09/10/nara-looking-for-public-input/#comments</comments>
		<pubDate>Tue, 11 Sep 2007 04:37:51 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[Congress]]></category>
		<category><![CDATA[NARA]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[archivist]]></category>
		<category><![CDATA[preservation]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/09/10/nara-looking-for-public-input/</guid>
		<description><![CDATA[The National Archives and Records Administration (NARA) is seeking public input into their draft plan for digitizing their content.  This plan builds on their 10 year strategic vision, published last year, and lays out their goals for moving more of their physical materials into a publicly available digital format.
I found Appendix A particularly interesting [...]]]></description>
			<content:encoded><![CDATA[<p>The National Archives and Records Administration (<a href="http://www.archives.gov/">NARA</a>) is <a href="http://www.archives.gov/comment/digitizing-plan.html">seeking public input</a> into their draft plan for digitizing their content.  This plan builds on their <a href="http://www.archives.gov/about/plans-reports/strategic-plan/">10 year strategic vision</a>, published last year, and lays out their goals for moving more of their physical materials into a publicly available digital format.</p>
<p>I found Appendix A particularly interesting (page 24), laying out their guidelines for partnerships with businesses and non-profits who will be taking on some of the immense digitizing.  The guidelines deal heavily with public access, intellectual property, metadata, and document certification issues, many of which I have only basic familiarity.</p>
<p>I assume that others will have opinions on how they&#8217;re proceeding, given the likely enormity of the project and the sheer importance of its subject matter.  That they&#8217;re welcoming public input is heartening:</p>
<blockquote><p>NARA takes its stewardship responsibility very seriously.  We recognize that we are entrusted with the care of AmericaÃ¢â‚¬â„¢s documentary evidence, and that these materials are an invaluable public resource.  We are seeking written comment on this draft through a Federal Register notice and announcement on our website, and will hold a public forum during the comment period.  We will revise this plan as appropriate to incorporate public comment.  The approved plan will be posted on our website at www.archives.gov.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/09/10/nara-looking-for-public-input/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>National Archives Video</title>
		<link>http://www.theopenhouseproject.com/2007/09/03/national-archives-video/</link>
		<comments>http://www.theopenhouseproject.com/2007/09/03/national-archives-video/#comments</comments>
		<pubDate>Tue, 04 Sep 2007 00:47:53 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[archivist]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[preservation]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/09/03/national-archives-video/</guid>
		<description><![CDATA[The National Archives (NARA, or National Archives and Records Administration) has a great video on their website, telling the story of citizens holding their government accountable through empowered investigation of public documents.
Check it out.
]]></description>
			<content:encoded><![CDATA[<p>The National Archives (NARA, or National Archives and Records Administration) has a great video on <a href="http://www.archives.gov/">their website</a>, telling the story of citizens holding their government accountable through empowered investigation of public documents.</p>
<p><a href="http://videocast.nih.gov/sla/NARA/dsh/index.html">Check it out</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/09/03/national-archives-video/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Senate Legislative Branch Appropriations Review</title>
		<link>http://www.theopenhouseproject.com/2007/08/23/senate-legislative-branch-appropriations-review/</link>
		<comments>http://www.theopenhouseproject.com/2007/08/23/senate-legislative-branch-appropriations-review/#comments</comments>
		<pubDate>Thu, 23 Aug 2007 17:20:59 +0000</pubDate>
		<dc:creator>John Wonderlich</dc:creator>
				<category><![CDATA[Congress]]></category>
		<category><![CDATA[OpenHouse]]></category>
		<category><![CDATA[appropriations]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[archivist]]></category>
		<category><![CDATA[committees]]></category>
		<category><![CDATA[government websites]]></category>
		<category><![CDATA[lobbying]]></category>
		<category><![CDATA[lobbying disclosure]]></category>
		<category><![CDATA[preservation]]></category>

		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/08/23/senate-legislative-branch-appropriations-review/</guid>
		<description><![CDATA[The Senate Legislative Branch Appropriations Bill (reported out of committee on June 21st) provides a revealing look into the priorities that Congress sets in funding its own operations.  The House and Senate pass separate appropriations bills; this page on THOMAS organizes the appropriations bills for each fiscal year in a remarkably useful manner.
While the [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://thomas.loc.gov/cgi-bin/bdquery/z?d110:S.1686:">Senate Legislative Branch Appropriations Bill</a> (<a href="http://thomas.loc.gov/cgi-bin/cpquery/R?cp110:FLD010:@1(sr089)">reported</a> out of committee on June 21st) provides a revealing look into the priorities that Congress sets in funding its own operations.  The House and Senate pass separate appropriations bills; <a href="http://thomas.loc.gov/home/approp/app08.html">this page</a> on THOMAS organizes the appropriations bills for each fiscal year in a remarkably useful manner.</p>
<p><img align="left" src="http://www.theopenhouseproject.com/wp/wp-content/uploads/senate-approps-jpeg.jpg" />While the majority side of the Senate Appropriations committee did include a <a href="javascript:openScript('download.cfm?file=2007%5F06%5F21%5FSenate%5F%20Appropriations%5FCommittee%5FClears%5FFiscal%5F2008%5FLegislative%5FBranch%5FFunding%5FLegislation%2Epdf&#038;dir=legislative',800,600)">brief review</a> of their bill (<a href="http://appropriations.house.gov/pdf/LegBranchHP.pdf">as did</a> their House counterpart), I&#8217;d like to give my impressions of the appropriations from the perspective of an advocate for public access and transparency, using the Senate report as a guide.  (The Republican websites don&#8217;t feature any press releases, which isn&#8217;t surprising, given the minority&#8217;s smaller staff and budget, comparative lack of clout in controlling committee functioning, and their opportunity to add dissenting views to the report, as I discovered in <a href="http://www.theopenhouseproject.com/2007/06/27/house-leg-branch-appropriations-review/">reading</a> the House report.)</p>
<p>Reading the <em>actual</em> report yields much greater detail about how our federal government views its own functions and prioritizes.  Committee reports are carefully structured documents, largely in response to the specific requirements of House Rule XIII, governing the explicit disclosure of legal wording, and the production and availability of reports.  Aside from raw statistical details comparing spending to the President&#8217;s budget requests (which the Leg. Branch subcommittees managed to stay below), the reports also afford an intimate view into the priorities and inner functions of the government.</p>
<p>The Senate report contains a similar admonishment against legislative branch waste, explaining the creation of an Inspector General for the Office of the Architect of the Capitol.  (p. 3, page numbers as numbered on the report).</p>
<p>The report similarly touts the passage of S.1, defending their spending power while asserting the benefits of transparency:</p>
<blockquote><p>The Committee believes trongly that Congress should make the decisions on how to allocate the people&#8217;s money.  In order to improve transparency and accountability in the process or approving earmarks (as defined in S. 1) in appropriations measures, each Committee report includes, for each earmark&#8230;[the Member's name, the location of the recipient, and the purpose for each earmark.] (p. 4)</p></blockquote>
<p>The report lists budgets and priorities for offices throughout the Senate, including the Office of Captioning Services, as authorized by Public Law 101-163.  I wonder if the likely public domain status of these captions could be leveraged to help provide a text stream to accompany internet based legislative video, to help with section 508 (accessibility) concerns for members posting videos of themselves on their websites?</p>
<p>Budgets for each Senatorial office are posted, ranging from about $2 million to about $4 million, depending on the size of the population of each state and the increased travel expenses associated with more distant states.</p>
<p>Each separate committee and administrative office has a detailed budget; within these estimates one can see that one year of utilities for the Capitol costs about $64.4 million.</p>
<p>The Library of Congress gets about $577 Million, and also gets castigated for apparent poor budgeting (p. 35)&#8230;</p>
<blockquote><p>The Committee continues to be concerned with the Library&#8217;s budget development process&#8230; The Committee recognizes improvements in the Library&#8217;s strategic planning efforts, but believes a better job needs to be done of setting priorities, recognizing budgetary constraints, and linking the budget to performance-based metrics.</p></blockquote>
<p>The LOC is an essential American institution, controlling and maintaining much of the information and knowledge that permits Congress to function.  The Congressional Research Service also gets singled out:</p>
<blockquote><p>It has come to the Committee&#8217;s attention that CRS has been holding annual management retreats at expensive off-site locations&#8230;  The Committee is also concerned that the Congressional Research Service often acts as if it were an independent agency, separate from the Library of Congress.  CRS is in fact part of the Library of Congress, and its policies and procedures should reflect this fact. (p. 39)</p></blockquote>
<p>Many of the report&#8217;s admonishments suggest strange issues or struggles whose origin is unclear to the observer.  For example, the restriction of public travel and occupancy of the LOC &#8220;to the sidewalks and other paved surfaces&#8221; is rescinded (p. 49).  I can only imagine what resulted in that particular rules change.</p>
<p>The Office of Technology Assessment come up in the Senate report again as well&#8230;</p>
<blockquote><p>The Committee recommends funding of $750,000 and four full-time equivalent employees to establish a permanent technology assessment function in the Government Accountability Office.  The Committee has decided not to establish a separate entity to provide independent technology assessment for the legislative branch owing to budget constraints&#8230;  (p. 42)</p></blockquote>
<p>The report goes into further detail about their plans for a revisited OTA (which was disbanded in the Gingrich revolution.  Background about the Open House Project and the OTA is available <a href="http://www.theopenhouseproject.com/2007/06/04/ota-endorsement/">here</a>.</p>
<p>The report also mentions the FDLP program under the Office of Superintendent of Documents, describing the distribution process of government documents.  (p. 42)</p>
<p>The amount of detail in appropriations reports is staggering, and Congress does a great service to anyone looking to understand where the government&#8217;s money is spent in providing detailed appropriations reports in human readable (non-legal) language.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.theopenhouseproject.com/2007/08/23/senate-legislative-branch-appropriations-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
