Home » Posts tagged 'born-digital' (Page 2)
Tag Archives: born-digital
Welcome Sitting Bull College Library to the FDLP!
Last week, GPO announced that Sitting Bull College Library had joined the Federal Depository Library Program (FDLP) and would be the first digital-only member of the FDLP. Welcome Sitting Bull College to the FDLP! But one sentence piqued my interest in GPO’s press release: “…opting to meet their community’s needs by developing an online Government […]
Lunchtime Listen: Born Digital Government Information
Back in April I gave a brief (18 minutes!) talk at the Center for Research Libraries Forum, Leviathan: Libraries and Government Information in the Era of Big Data. Here are the slides and the audio recording of that presentation: Government Records and Information: Real Risks and Potential Losses. The presentation gave me an opportunity to […]
Born-Digital U.S. Federal Government Information: Preservation and Access
The paper that I prepared under contract for the Center for Research Libraries is now available: Born-Digital U.S. Federal Government Information: Preservation and Access, March 2014. Prepared by James A. Jacobs for “Leviathan, the Center for Research Libraries Global Resources Collections Forum.” [link updated] This is one of several background readings recommended by CRL for […]
Crazy born digital content
One of the best things that could happen for digital preservation is for producers of digital content to understand that they need to produce preservable content. If producers and publishers created digital content in neutral, preservable formats, we would not have to spin our wheels with the Sisyphean task of constantly trying to fix un-preservable content with techniques such as emulation and format migration. For publishers (and of course this includes government agencies) to create preservable content, they would have to understand that their essential role in the information lifecyle includes creating information that is preservable -- not just instantaneously deliverable in the short-term. Although there are efforts to develop this understanding and to create appropriate formats and processes, most born-digital information seems to be generated with only the most short-term utility in mind. A lot of born digital content is badly-formed and uses non-standard, proprietary, and closed formats. All that brings me to this example of what looks to be shoddy content creation.
- 2011 U.S. Intellectual Property Enforcement Coordinator Annual Report On Intellectual Property Enforcement. U.S. Intellectual Property Enforcement Coordinator, March 2012.
In June 2010, the Administration, through the IPEC‘s Joint Strategic Plan, emphasized the protection and enforcement of U S intellectual property rights These rights drive the economy, create jobs for American workers, promote innovation, and secure America’s position as the world’s leader for creativity and ingenuity The 2011 Annual Report provides an illustration of the coordinated efforts that the U S Government is undertaking to address the challenges of enforcing intellectual property of U S rightholders abroad, securing supply chains, pursuing sources of counterfeit and pirated goods, and meeting the challenges posed by emerging criminal trends such as the online sales of counterfeit pharmaceuticals, economic espionage, and targeted theft of trade secretsThis is probably just some odd, unique production mistake. But that is the point: When an agency cannot even take the time to make sure its born digital text has periods at the end of sentences, how can we expect agencies to produce digital content that conforms to preservation technology requirements? There is a lot of work to be done before we can ensure the public that we can preserve digital government information! (Hat tip to Mike Masnick who, in a highly critical review of the report, says, with tongue in cheek, that the reason the report "seems to do away with the grammatical icon known as 'the period' at the end of sentences" might be that the Intellectual Property Enforcement Coordinator found it "too expensive to license.") Continue reading
Latest Comments