skip navigation
  • Ask a LibrarianDigital CollectionsLibrary Catalogs
  •  
The Library of Congress > Preservation > Resources > Recommended Formats Statement
Preservation
  • Preservation Home
  • About
  • Collections Care
  • Conservation
  • Digital Preservation
  • Emergency Management
  • En Español
  • FAQ
  • Preservation Science
  • Resources
  • Outreach & Training Opportunities
  • Have a preservation question?
    Ask-a-Librarian

Related Links

  • Donate
  • Blog: Guardians of Memory, Preserving the National Collection
  • Audio-Visual Preservation
  • National Film Preservation Board
  • National Recording Preservation Board

Recommended Formats Statement


{ subscribe_url: '/share/sites/Bapu4ruC/preservation.php' }
« Back to Recommended Formats Statement
Main | Table of Contents | Introduction | Summary of Digital Format Preferences | Textual Works | Still Image Works | Moving Image Works | Audio Works | Musical Scores | Datasets | GIS, Geospatial and Non-GIS Cartographic | Design and 3D | Software and Video Games | Web Archives | Email

IX. Software and Video Games

This category includes software for Desktop, Mobile/Handheld and Video Gaming Systems. Note: Gaming Systems often require submission of the proprietary platform as well (e.g. Game console) or a virtual or emulated version of the proprietary platform that runs on a commonly available operating system.

i. Software and Video Games
Software and Video Games
  Preferred Acceptable
A. Content, in order of preference
  1. Uncompiled Source Code: A file-based copy of the source code from which the software was developed. Metadata that specifies which compiler was used to create the final code for commercial release—including the version number and build number of the compiler software—must be included. If the compiler is unique to the project or company (i.e. not commercially available), then a copy of compiler software in the specific version and build used to create this version of the software, along with specifications of the platform the compiler ran on, must be included in the submission. This submission should include the rights clearance for the Library to install and use the compiler to read and use the provided information.
  2. Gold master build (specific file types will vary depending on company producing build)
  3. Distribution file (e.g. ipa [Mac iOS], apk [Android], exe [Windows])
  4. Disk-based physical release of game/software content

Hard drive/flash drive/writable disk of game/software content

B. Operating system

Operating system: If not a commonly available OS, then a copy of the OS, submitted as a disk image, must be provided with the submission. 

NOTE: If there are different versions released at the same time for different operating systems (e.g. for Mac, Windows and Xbox One), a submission will be required for each.

 
C. Platform

If a submission requires a stand-alone or proprietary platform (e.g. a gaming system or child’s toy), then a virtual or emulated version of the proprietary platform is required with submission.

If a submission requires a stand-alone or proprietary platform (e.g. a gaming system or child’s toy), and a virtual or emulated version of the proprietary platform is not available, a physical platform including controllers and power supply is acceptable.

D. Related materials

With documentation and other accompanying material (e.g. instruction materials, errata, addenda, read me files). A copy of the electronic distribution file if the product was sold to the public as a downloadable file. Note: if the software was a part of a book publication (e.g. a software manual with accompanying discs), then a copy of the book must be submitted with the disc.

 
E. Delivery method

Direct File Submission: These submissions would require grouping in a submission package such as BagIt, Tape Archive (tar), or AXF object.

Mass storage device: All of the requested information may be included as distinct files or may be grouped together using a method such as BagIt, Tape Archive (tar), or AXF object
  • Hard drive with USB (universal serial bus) interface
  • CD-ROM disc
  • Flash drive with USB interface
  • DVD disc
F. Metadata
  1. Metadata that specifies which compiler was used to create the final code for commercial release—including the version number and build number of the compiler software—must be included.
  2. As supported by format:
    1. Title
    2. Creator
    3. Creation date
    4. Place of publication
    5. Publisher/ producer/ distributor
    6. Contact information
    7. Production metadata such as credit, rights and files which are available at the time of production
  3. Include if available:
    1. Language of work
    2. Other relevant identifiers (e.g., UPCDOI, LCCN, etc.)
    3. Subject descriptors
    4. Abstracts
    5. Schema
 
G. Technological measures

Submissions of uncompiled source code must include the rights clearance for the Library to install and use the compiler to read and use the provided information.

Files must contain no measures (such as digital rights management technologies or encryption) that control access to or prevent use of the digital work.)

A file containing digital rights management technologies or encryption which requires a stand-alone or proprietary platform is accompanied by a virtual or emulated version of the proprietary platform or a physical version of the platform.

However, the file cannot include a connection to a remote server for DRM or encryption services.

Back to Top

Stay Connected with the Library All ways to connect »

Find us on

PinterestFacebookTwitterYouTubeFlickr

Subscribe & Comment

  • RSS & E-Mail
  • Blogs

Download & Play

  • Podcasts
  • Webcasts
  • iTunes U 
About | Press | Jobs | Donate | Inspector General | Legal | Accessibility | External Link Disclaimer | USA.gov | Speech Enabled Download BrowseAloud Plugin