The Sunlight Foundation Blog
 
  • Library of Congress on Flickr

    POSTED BY
    John Wonderlich

    You should proceed as soon as possible to check out the Library of Congress’s page on flickr, as announced this morning.

    It’s an awesome collection of about 3,000 images, of the quality you’d expect from the world’s largest library. It’s wonderful to see them available the same way we expect to share images with each other, sort of making history less of something living in a museum, and more of something available, relevant, and even sorted through tags.

    If you’re like me, you’re likely to do nothing else for the next hour or two… 

    0 Comments

    Posted: January 16th, 2008 Tags: ,
  • Bibliographic Control, Agile Government

    POSTED BY
    John Wonderlich

    I found this post from the Library of Congress blog yesterday, and it has me thinking about a bunch of other things I’ve been intending to write about. The LOC is accepting public commentary on their draft plan for the Working Group for the Future of Bibliographic Control. The draft is full of noteworthy observations about decentralized information management and the Internet, and I’m going to excerpt from it generously below.

    First, however, I’d like to point to another report I recently came across, called Agile Government: A Provocation Paper. Prepared in conjunction between Demos and the State of Victoria (an Australian state), the paper applies the concept of agility (as often applied to software development) to public sector planning. Agility focuses on the productively dynamic aspects of management, development, and administration, stressing iterativeness and flexibility over comparatively static organizational models.

    While I’m personally unconvinced by the idea of agility as a fundamental organizational principle, and prefer to think of it as a helpful rubric or theme, the concept does provide a helpful lens with which to view other government documents which are broad in scope.

    For example, when I wrote recently about the National Archives’ public comment period for their partnership plan for digitization, I was most impressed by the public, iterative nature of the projects’ planning. A superior plan will presumably result if the plan is skillfully subjected to multiple periods of public inspection and re-editing. This process’s constructive aspects are echoed in both the organization of the Open House Project report, and in the legislative process itself.

    I’m wondering about the history of public administration’s public components, that is, when did certain plans start to be subjected to public commentary? For how long has the federal regulatory process been subject to public commentary? For how long have legislative support agencies been publishing 10 year visions and yearly updates? Perhaps most importantly, what is the best way to optimize and institutionalize the benefits of publishing organizational plans? Is a statutory mandate necessary, or are modern expectations of effective management practices sufficient? Does the public benefit from a required level of visionary reporting from its institutions, or should the agencies report on their activities in whatever manner best fits their needs? Does the reporting of such documents currently outpace the public demand for such information?

    I hope it doesn’t: I’d prefer to think that the GPO’s or NARA’s visions for digitization don’t go unnoticed, that the LoC’s enormous yearly updates are appreciated for their scope and detail, that the strategic visions (of approximate 10 year length) of GPO, NARA, the LOC, or the frequent reports from the CAO, CRS, NARA, or various related Inspectors General (GPO, LoC) are at least perused by the parties affected. Surely a demand for information and awareness necessary for a government to be agile must be coupled with a community of information consumers who are aware of that information?

    Back to the topic at hand, the Library of Congress has a public report currently in a public comment phase, looking for feedback on their vision about the future of the Library (and especially their bibliographic activities, especially as it relates to cataloging and metadata) in an age of digital Internet publishing and information dissemination. While the report deals extensively with the minutae of the LOC’s information management practices, it also provides repeated insight into the Library’s view of a rapidly changing information ecology, reinforcing many observations and concerns shared throughout the Open House Project (and broader) community. (also adding to a previous plan by the LOC regarding bibliographic control.)

    From the introduction:

    The future of bibliographic control will be collaborative, decentralized, international in scope, and Web-based. Its realization will occcus in cooperation with the private sector, and with the active collaboration of library users.

    Page 2:

    Recognize that people are not the only users of the data that we produce in the name of bibliographic control, but so too are machine applications that interact with those data in a variety of ways.

    Page 3:

    In 1902, the Library of Congress began producing catalog cards for purchase so that libraries that purchased the same book could buy catalog cards from the Library of Congress… The service continues to this day, although now bibliographic data are in machine-readable form and are shared over networks.

    Page 4:

    The economics of creating LC’s products have changed dramatically since the time when the Library was producing cards for library catalogs.

    …it receives no funding specifically directed at providing bibliographic services for U.S. libraries.

    Page 7:

    …it is necessary to embrace a view of bibliographic control as a distributed activity, not a centralized one. Data about collection usage–such as inclusion in curricula or bibliographies, citation links, circulation and sales figuresl–are all valuable bits of information in the universe of bibliographic control.

    Page 8:

    All possible means of collaboration should be considered. …needs to consider carefully when it is appropriate to distribute effort and when to discontinue it.

    Page 9:

    …the standards landscape in the library field is murky, with many different organizations working on similar standards in a non-coordinated fashion. LC should consider sharing the standards effort within the community and collaborating with other interested institutions to create a rational and efficient means of managing the standards needed for information exchange.

    Page 21:

    2.4.1 LC: Study possibilities for computational access to digital content. Use this information in developing new rules and best practices.

    Page 22:

    The use of language strings such as personal or corporate names as identifiers hinders data exchange across languages and across different information communities.

    3.1.1 Develop a More Flexible, Extensible Metadata Carrier

    Page 24:

    New discovery environments are emerging that extract and merge data from several library systems.

    0 Comments

    Posted: December 2nd, 2007 Tags: , , ,
  • Library of Congress Website Upgrade

    POSTED BY
    John Wonderlich

    Via the Library of Congress blog, it looks like the LOC Website will be getting an upgrade in the coming weeks. They make a good point about choosing between providing RSS feeds and email updates, noting that many more people use email than RSS:

    While only a fraction of people on the Web use RSS feeds, something like 100 percent of them use email, and this is just another part of our efforts to get information to people in the way that is most useful to them. You can get a sense for how the email updates will function by looking at the FBI’s Web site.

    Happily, they’re not choosing between the two, and have a pretty broad set of RSS feeds already on offer on their RSS page.

     

    Of particular note on the existing RSS feeds are the LOC blog feed (whereby I noticed this update post), the digital preservation feed, a legislation update feed from the Copyright office (I wonder if other agencies are doing this?), and a feed of Federal Register items relevant to the Copyright office. (I’m also curious as to the degree of automation in gathering agency specific items to form these feeds. How are they set up, and from where are they gathered? What would it take to reproduce this in other agencies?) Looks like NARA’s got three feeds set up: news and events, today’s document, and Federal Register Documents on public inspection.

    The GAO has a great offering as well.
    Could the GPO or CAO be close behind?

    Know of any other forward looking government information sources?

    (Crossposted from the Open House Project blog.)

    0 Comments

    Posted: August 30th, 2007 Tags: , , , ,
  • Senate Legislative Branch Appropriations Review

    POSTED BY
    John Wonderlich

    (Cross-posted from the Open House Project blog.)

    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 majority side of the Senate Appropriations committee did include a brief review of their bill (as did their House counterpart), I’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’t feature any press releases, which isn’t surprising, given the minority’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 reading the House report.)

    Reading the actual 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’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.

    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).

    The report similarly touts the passage of S.1, defending their spending power while asserting the benefits of transparency:

    The Committee believes trongly that Congress should make the decisions on how to allocate the people’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…[the Member’s name, the location of the recipient, and the purpose for each earmark.] (p. 4)

    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?

    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.

    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.

    The Library of Congress gets about $577 Million, and also gets castigated for apparent poor budgeting (p. 35)…

    The Committee continues to be concerned with the Library’s budget development process… The Committee recognizes improvements in the Library’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.

    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:

    It has come to the Committee’s attention that CRS has been holding annual management retreats at expensive off-site locations… 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)

    Many of the report’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 “to the sidewalks and other paved surfaces” is rescinded (p. 49). I can only imagine what resulted in that particular rules change.

    The Office of Technology Assessment come up in the Senate report again as well…

    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… (p. 42)

    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 here.

    The report also mentions the FDLP program under the Office of Superintendent of Documents, describing the distribution process of government documents. (p. 42)

    The amount of detail in appropriations reports is staggering, and Congress does a great service to anyone looking to understand where the government’s money is spent in providing detailed appropriations reports in human readable (non-legal) language.

    0 Comments

The Site may contain links to Internet sites that are not operated by Sunlight Foundation. These links are provided as a service and do not imply any endorsement of the activities or content of these sites, nor any association with their operators. Sunlight Foundation does not control these Internet sites and is not responsible for their content, security, or privacy practices. We urge you to review the privacy policy posted on web sites you visit before using the site or providing personal information.


The content of this site, where applicable, is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License.