Top Banner
2013 Legislative Data and Transparency Conference
97

2013

Feb 25, 2016

Download

Documents

zaina

Legislative Data and Transparency Conference . 2013. Conference Schedule. Legislative Overview. Kirsten Gullickson Office of the Clerk. Legislative Process Overview. Kirsten Gullickson , Sr. Systems Analyst Office of the Clerk. Rep. Ludlow placing bill into hopper 12/30/1936 - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 2013

2013

Legislative Data and

TransparencyConference

Page 2: 2013

Conference ScheduleLegislative Process OverviewLegislative Branch UpdateBulk Data Task Force update on provisioning legislative dataLibrary of Congress and GPO Electronic Access Plans and DevelopmentsOfficial Tools Demo - Administrative Interface (docs.house.gov) - Democratic Caucus Intranet - Committee Roll Call Vote UtilityInternational UpdateElectronic Legislative Archiving:Panel of legislative archivists discuss how to preserve and curate electronic legislative recordsExtending Legislative XML for and by third parties:Address XML data standards and how to extend them for new applicationsUnder-digitized legislative data:What are the evolving standards and practices for integration and use of legislative data?

Page 3: 2013

Legislative Overview

Kirsten Gullickson

Office of the Clerk

Page 4: 2013

Legislative Process Overview

Kirsten Gullickson, Sr. Systems Analyst

Office of the Clerk

Rep. Ludlow placing bill into hopper 12/30/1936http://www.loc.gov/pictures/item/hec2009008605/

Page 5: 2013

The Challenge• Legislative documents and related data

must be– prepared– managed,– distributed, and– archived.

• This includes paper and electronic means for handling the official documents.

Page 6: 2013

How a bill become a law. After the vote has been taken, the result is noted in the Journal of Action by Louis Sirkey, House Journal Clerk. If the bill receives a passing vote, it is sent to the other chamber for action. If the bill failed to pass it must be reintroduced unless it is voted to refer it back to the committee for reconsideration

Page 7: 2013

The Challenge (cont’d)Government data should be

– Public– Accessible– Described– Reusable– Complete– Timely– Managed Post-Release

White House M-13-13, Open Data Policy, Managing Information as an Asset

Page 8: 2013

Where are the documents? Data?

•GOVERNMENT PRINTING OFFICE

– www.gpo.gov

•LIBRARY OF CONGRESS

– Thomas.loc.gov– Beta.congress.gov

•THE HOUSE– Clerk.house.gov– Docs.house.gov– www.house.gov– Committee websites

•THE SENATE– www.senate.gov– Committee websites

Page 9: 2013

General Document Flow

Page 10: 2013

Introduction and Referral to Committee

Doc. 110-49, page 8How Our Laws Are Made

http://history.house.gov/Collection/Listing/2004/2004-019-000/

The Hopper

Page 11: 2013

Consideration by Committee

Doc. 110-49, page 11How Our Laws Are Made

Page 12: 2013

Reported to House and Placed on Calendar

Doc. 110-49, page 15How Our Laws Are Made

Page 13: 2013

Consideration on House Floor

Doc. 110-49, page 20How Our Laws Are Made

Page 14: 2013

Senate Consideration

Doc. 110-49, page 36How Our Laws Are Made

Page 15: 2013

Enrollment and Presidential Actions

Doc. 110-49, page 36How Our Laws Are Made

Page 16: 2013

Slip laws and U.S. Code

Doc. 110-49, page 53How Our Laws Are Made

Page 17: 2013

Questions and Answers

Until Jurgensen, Jr., a tally clerk designed this electric voting machine it took at least three months, using the old rubber stamp system, to compile the voting records of the 435 members of the House. Recording the yeas and nays, absent and present, paired for and paired against votes of each individual member, the machine which is similar to an adding machine, does the same job in less than two weeks. Greater accuracy is assured in counting votes with Jurgensen-designed machine.

New time saving voting machine 05/10/1938http://www.loc.gov/pictures/item/hec2009015711/

Page 18: 2013

Bulk Data Task Force Update

Robert ReevesOffice of the Clerk

Page 19: 2013

Bulk Data Task Force and Transparency Updates

Since our last meeting on January 30, 2013 here’s what we’ve been up to:

Page 20: 2013

Bulk Data Task Force and Transparency Updates

Page 21: 2013

Bulk Data Task Force and Transparency Updates

Page 22: 2013

Bulk Data Task Force and Transparency Updates

Page 23: 2013

Bulk Data Task Force and Transparency Updates

Other projects:• Bulk Data Bill Summaries• House Modernization Project• Data Challenge• Data Dashboard• Clerk Twitter Account• Clerk/History Arts & Archives YouTube

Page 24: 2013

Library of Congress and GPO Plans and Developments

Tammie NelsonLibrary of Congress

Matt LandgrafGovernment Printing Office

Page 25: 2013

LIBRARY OF CONGRESSTammie Nelson

Page 26: 2013

GPO/LOC Collaboration: Digitization of Core Legislative Materials

Matt Landgraf - GPO

May 22, 2013

Page 27: 2013

Background

Joint Committee on Printing approved collaboration on digitization of:

Statutes at Large

Bound Congressional Record

Page 28: 2013

Roles and Responsibilities

Library of Congress:

Performs digitization

Provides files to GPO

GPO: Creates access copies

Creates metadata

Page 29: 2013

Statutes at Large Status

All work for volumes from 1951-2002 has been completed

Currently available via FDsys

Access files and metadata have been provided to LOC (to be available on congress.gov in the future)

Page 30: 2013

Bound Congressional Record Status

LOC Digitization (1873-1998) to be completed by the end of calendar year 2013

FDsys development underway

Resources being identified for metadata creation

Content will be released on an iterative basis via FDsys, beginning in FY 2014

Page 31: 2013

Bound Congressional Record: Key Issues

Size of collection

Large effort required to create descriptive metadata and access files at the article level

Page 32: 2013

Official Tools Demonstration Panel

Michael BakerHouse Committee on Ways and Means

Stephen DwyerOffice of the Democratic Whip

Kathleen SwiatekGovernment Printing Office

Page 33: 2013

The Official Intranet for House Democratic Staff

Presentation by Steve Dwyer, Office of the Democratic Whip

Page 34: 2013

HISTORY & ORIGIN

• Originally launched in early 2009• We recently launched our 3rd major iteration• Private—only House Democratic staffers

have access• Why did we build it? • Why Democrats-only?

Page 35: 2013

ORGANIZATION• Over 120,000 nodes and counting• How do we organize content?

• Primarily by legislation• General issue tags• “Specific Topics” for big non-bill items• Authoring office and staffer

Page 36: 2013

DATA SOURCES UTILIZED• GovTrac for legislative information• House LDAP for permissions and

credentials• Housenet’s e-Dear Colleague system• DemocraticWhip.gov for House Floor

schedule

Page 37: 2013

DATA SOURCES UTILIZED (CONTINUED)

• Docs.house.gov for Committee schedules

• POPVOX for organization letters and public sentiment

• Staffer data from a commercial vendor• Significant private listservs are auto-

consumed

Page 38: 2013

The Official Intranet for House Democratic Staff

Presentation by Steve Dwyer, Office of the Democratic Whip

Page 39: 2013

International Update

Gherardo Casini

Global Center for ICT

Page 40: 2013

Electronic Legislative Archiving Panel

James JacobsGovernment Information Librarian, Stanford Univ.

Lisa LaPlantGovernment Printing Office

Marc LevittByrd Center for Legislative Studies

Page 41: 2013

Preserving Electronic Legislative Information in FDsys

Legislative Data Transparency ConferenceMay 22, 2013

Lisa LaPlantGPO

Page 42: 2013

GPO’s MissionKeeping America Informed by producing, protecting, preserving, and distributing the official publications and information products of the Federal Government.

1

Page 43: 2013

2

Page 44: 2013

3

Legislative Publications Bills and Resolutions Committee Materials Congressional Calendars Congressional Directory Congressional Record United States Code Journal of the House of Representatives Procedural and Precedential Materials

Page 45: 2013

4

Digital Preservation Combination of the policies, strategies, and actions that ensure access to reformatted and born digital content regardless of the challenges of media failure and technology change.

Page 46: 2013

5

Preservation Goal Accurately render authenticated content over time.

Page 47: 2013

6

Preservation Objectives Safeguard digital content along with all relevant metadata. Assess the condition and needs of collections of digital information. Meaningfully render content despite continuously changing technology. Manage processes which are auditable, replicable, and that build the basis for trust.

Page 48: 2013

OAIS Reference Model

7

Consumer

Producer

System Administration

Ingest Access

Data Management

ArchivalStorage

Preservation Planning

Page 49: 2013

Package Based Approach

8

Package 1

Rendition 2

ContentFiles

mods.xml

aip.xml

premis.xml

Rendition 1

ContentFiles

Page 50: 2013

9

PREMIS Record each significant event in the lifecycle of content in PREMIS metadata. Record the content source, changes that have occurred since the content was created or acquired, and who has custody of the content.

Page 51: 2013

Events Recorded in PREMISSoftware Activities: Digest Calculation Ingest Fixity Check Rendition Creation ACP Creation Digital Signing Parsing

User Activities: Rendition Upload Rendition Deletion Submission Replacement AIP Deletion

10

Page 52: 2013

11

Preservation Strategies Refreshment (bit-level preservation)

Content is transferred from one physical medium to another.

MigrationContent is converted or transformed into a more recent version or a more widely used format. 

Page 53: 2013

FDsys Primary and COOP

12

Page 54: 2013

13

More InformationLisa LaPlantOffice of Programs, Strategy, and Technology, [email protected]

GPO’s FDsyswww.fdsys.gov

Preservation in FDsyswww.gpo.gov/preservation

Page 55: 2013

Archiving Senator Byrd’s E-Records

Marc LevittDirector of Archives

Robert C. Byrd Center for Legislative Studies

Page 56: 2013

Records Received & Migrated• Early Petitions (1790-1817)- PDFs with OCR• Byrd Migration Projects:

– Photographs- TIFF– A/V Material- Outside Vendor– Microfilm- PDFs, then OCR (in-house)

• Byrd Capture Projects:– CSPAN floor speeches– Congressional Record PDFs

• Byrd Office Files Received: – Hard drive with files from the shared drive– Constituent Services System (CSS) data on 2 DVDs

Page 57: 2013

Case Study: CSS Processing• Hired a contractor• Script to automate ingestion of data• CSV tables cleaned and optimized with

Google Refine• SQL database created• Waiting for installation

Page 58: 2013

What the Office Uses:

Senator Byrd confers with President Jimmy Carter at the White House. (August 23, 1977). Official White House Photo.

Page 59: 2013

What is Archived by the Vendor:• <A color photograph of Senator Byrd (left) and

President Carter discuss issues in an office.>• <Senator Byrd is seated on a floral print

couch.>• <President Carter is seated on a blue chair.>• <Flower curtains hang behind the men.>• <A white lamp sits on a brown table between

them.>

Page 60: 2013

The Reconstructed Result:

Page 61: 2013

Not the Same:

Full picture and functionality in original record

Loss of information and context through 3 phases of data migration

Page 62: 2013

Issues• Authenticity and Reliability• Standardization• Organization Schema• What to Save (and why it’s okay to do so)

Page 63: 2013

Third Party Extensions of Legislative XML Panel

Daniel BennetteCitizen

Jim HarperCATO Institute

Eric MillSunlight Foundation

Page 65: 2013

Extending Congressional XML:

Transparency, Soup to Nuts

Page 66: 2013

Extending XML

“Soup to Nuts”

- American English idiom conveying the meaning of "from beginning to end“- Derived from the description of a full course dinner, in which courses progress from soup to a dessert of nuts

Page 67: 2013

Extending XML

“Deepbills” Project

CatoXML

http://www.cato.org/resources/data

Page 68: 2013

Extending XML

Page 69: 2013

Extending XML

Page 70: 2013

Extending XML

Page 71: 2013

Extending XML

Page 72: 2013

Extending XML

Page 73: 2013

Extending XML

Page 74: 2013

Extending XML

Page 75: 2013

Extending XML

Page 76: 2013

Extending XML

What can YOU build?

Page 77: 2013

Extending XML

“Deepbills” Project

CatoXML

http://www.cato.org/resources/data

Page 78: 2013

Under-digitized Legislative Data Panel

Anne WashingtonGeorge Washington University

Grant VergottiniXcential, Inc.

Josh TaubererGovTrack

Page 79: 2013

Why Digitize?Anne L. Washington, PhD

George Mason University, School of Public Policy

May 2013Legislative Data Standards Conference

US House of Representatives

Page 80: 2013

Political InformaticsPoli-Informatics• Computational science & "big data"

– Data visualization– Machine learning

• Study of politics and government

http://poliinformatics.org

Page 81: 2013

Poli-Informatics could…• Visualize complex policy solutions.• Predict procedural progress through

language.• View nested organizational hierarchies

impacted by a policy.• Gather single policy idea across multiple

ideological discourses.• Track policy developments over time.

Page 82: 2013

Joint PI-net• George Mason University • University of Washington• Northwestern University• Cornell University• Carnegie Mellon University• Pennsylvania State University• & YOU !

Page 83: 2013

http://poliinformatics.orgAnne L. Washington, PhD

http://washington.gmu.edu

[email protected] Professor

School of Public PolicyOrganizational Development & Knowledge

ManagementGeorge Mason University, Arlington VA

Page 84: 2013

Digitizing Legislative DataFrom documents to data to

information and beyond

Grant Vergottini

May 22, 2013

Page 85: 2013

Digitizing Legislative Data From documents to data to information and beyond

Now

Web Services

XML Download

Data Scraping

Proprietary XML

Open XML Standards-Based XML

Past

Akoma Ntoso

Future

Page 86: 2013

Step 1: Legislative Documents OnlinePutting the documents online

Data Scraping

Proprietary XML

Past

• Simple systems• Geared towards people rather than

programs

• Data Scraping for programs• Roll your own XML• Maintain your own repository

Page 87: 2013

Step 2: Legislative Data Sources Improving data accuracy

XML Download

Data Scraping

Open XMLProprietary XML

Past

• Authentic data• More sophisticated

Web Sites

• Download XML directly

• Open Gov. data formats

• Still need your own repository

Now

Page 88: 2013

Now

Next: Legislative Information Services

Future

Web Services

XML Download

Proprietary XML

Open XML Standards-Based XML

Past

Akoma Ntoso

Page 89: 2013

Step 3: Legislative Information ServicesConnecting the information

Web Services

Standards-Based XML

• More reliable data• Authentic HTML & XML

• More useful data• Consumer rather than producer

oriented• Simpler standards-based information

models• Linked citations & other metadata• Microformats & Microdata for HTML

• More timely data• Web services rather than download• Link services stitch data together• Robust repository services – search,

query

Akoma Ntoso

Future

Page 90: 2013

Step 4: The VisionConnecting the world

• State & Federal Laws

• Regulations to Legislation

• Treaties & Trade Agreements

Page 91: 2013

So what’s left to do?

Joshua Tauberer (@JoshData)GovTrack.us

Legislative Data & StandardsMay 22, 2013

Page 92: 2013

All legislative events are recordedin structured data.

All legislative artifacts arepublicly available.

(How hard could that be, right?)

Page 93: 2013

Legislative DataBill Summary & StatusAmendment Status & TextList of MembersCommittee ArtifactsHistorical Bill Text, Statutes, and so on.

Page 94: 2013
Page 95: 2013

http://opengovdata.io/maturity/

Page 96: 2013

Wrapping Up

Reynold Schweickhardt

Director of TechnologyCommittee on House Administration

Page 97: 2013

Thank you for participating!

Legislative Data and

TransparencyConference