GPO's Federal Digital System (FDsys) Briefing

10
GPO’s Federal Digital System (FDsys) Briefing Mike Wash [email protected] July 25, 2009

Transcript of GPO's Federal Digital System (FDsys) Briefing

Page 1: GPO's Federal Digital System (FDsys) Briefing

GPO’s Federal Digital System (FDsys) Briefing

Mike [email protected]

July 25, 2009

Page 2: GPO's Federal Digital System (FDsys) Briefing

1

• Access to government published information is now widely expected to be electronic

• Digital information needs to be authentic and verified to be the correct version

• Digital information needs to be available for access almost immediately

• Information needs to be preserved, making it available for generations to come

GPO needed a system to support existing and emerging market needs for quick, easy, and accurate access to government information.

Challenges in the Digital Age

Page 3: GPO's Federal Digital System (FDsys) Briefing

2

FDsys – GPO’s answer• FDsys automates the collection and dissemination

of electronic information from all three branches of government.

• Information is: – Submitted directly into FDsys – Permanently available in electronic format– Authenticated and versioned – Publicly accessible for searching and downloading– Available for conventional and on-demand printing

Page 4: GPO's Federal Digital System (FDsys) Briefing

3

The FDsys Difference• FDsys is a Content Management System

– FDsys securely controls digital content throughout its lifecycle to ensure content integrity and authenticity

• FDsys is a Preservation Repository– FDsys follows archival system standards to

ensure long-term preservation and access of authentic digital content

• FDsys is an Advanced Search Engine– FDsys combines extensive metadata creation

with modern search technology to ensure the highest quality search experience

Page 5: GPO's Federal Digital System (FDsys) Briefing

4

How FDsys Works

Producer

Content &Metadata

Access

SearchResults

Queries

Archival Storage

Ingest Data Management

GPOUsers

OrderInformation

Government Agencies &

U.S. Congress

Content & MetadataValidation

Authentication,Indexing &

Preservation

Cataloging,Search

Engine &Reference

Tools

GPOUsers

Consumer

EndUsers

Content &Metadata

Results

Queries

Content & MetadataStorage

Trusted Repository

Page 6: GPO's Federal Digital System (FDsys) Briefing

5

FDsys main page

Page 7: GPO's Federal Digital System (FDsys) Briefing

6

Sample search results

Page 8: GPO's Federal Digital System (FDsys) Briefing

7

Signed Bill with Signature Panel

Page 9: GPO's Federal Digital System (FDsys) Briefing

8

Quotes From FDsys Users

“I had an extremely difficult law question. I decided to try the question in FDsys and found the answer! My patron was mistaken. His source was not the US Code, but rather the CFR.”

“The system was thoughtfully presented. I like the way you presented the search on all or specific documents or content. Linking with all content within context of search results is a good idea.”

“I'm very optimistic about this product. It's obvious that a lot of energy has been put into it and I wish I could add it to my toolkit for government documents now! Please keep me on your list of future beta testers”

Presenter
Presentation Notes
1. How many docs are currently in FDsys? Packages: 164,228 Documents: 163,359 2. Are all of them authenticated? Congressional Bills, Public and Private Laws, and the Budget of the United States Government have been digitally signed are currently available on FDsys. The following collections will go live with digital signatures. Congressional Record Bound Statutes at Large Congressional Directory Government Manual GPO is moving forward with signing the following collections that are currently available in FDsys. Federal Register Congressional Record Congressional Reports Daily Compilation of Presidential Documents 3. What's our roll out on FDsys? FDsys is being rolled out in a series of releases. The first public release of FDsys was launched on January 15th. This release built the foundational infrastructure and began the replacement of the current public site (GPO Access). Subsequent releases will enable submission of content from congress and federal agency customers, automate preservation processes, and tailor FDsys to better meet individual user needs. 4. Has the roll out been successful? The rollout has been extremely successful. We've received positive feedback from GPO stakeholders, including strategic partners such as OFR and the library community.
Page 10: GPO's Federal Digital System (FDsys) Briefing

9

• Migration of the remainder of GPO Access content– All collections added by September 2009– FDsys will replace GPO Access at the end of the migration

period– Backup instance of FDsys completed and installed at the

ACF late fall 2009• Implementation of remaining FDsys Releases

– Release 2- Direct Congressional submission of information to GPO/FDsys (late 2009)

– Release 3- Direct agency submission of information to GPO/FDsys (mid 2010)

Path Forward

Presenter
Presentation Notes
5. What feedback have we gotten about FDsys? Since launch, we have received more than 300 comments on FDsys and they have been overwhelmingly positive. Many suggestions for improvement have already been implemented or are planned for future releases. Users are eagerly awaiting the launch of additional collections. 6. What collections are currently available? Compilation of Presidential Documents Congressional Bills Congressional Documents Congressional Hearings Congressional Record Congressional Reports Federal Register Public and Private Laws Budget of the United States Government List of CFR Sections Affected Economic Indicators Congressional Calendars Congressional Committee Prints 7. What are the next priority collections? History of Bills Congressional Record Index Economic Report of the President Congressional Record Bound GAO Reports and Comptroller General Decisions Statutes at Large Congressional Directory Government Manual U.S. Code Code of Federal Regulations Public Papers of the President 8. What are we doing about granular authentication? We are breaking large PDF documents into many smaller documents and applying digital signatures to the smaller documents.