Sector(s)
Team Members
The Barack Obama Presidential Library is the 14th Presidential library administered by the National Archives and Records Administration (NARA), a federal agency.
Unlike other Presidential Libraries administered by NARA, plans are for the Barack Obama Presidential Library to be the first fully digital presidential library. An estimated 95 percent of the Presidential records of the Obama administration were born-digital, such as photos, videos, word processing documents, tweets, emails, and other common digital formats. NARA and the Obama Foundation had intended to work together to digitize the unclassified textual Presidential records to create a digital archive. Unfortunately, the COVID-19 pandemic has impacted these plans.
NARA will process textual records in a traditional manner, with archival staff processing responsive textual records requested via FOIA from the textual record. NARA will then digitize these processed records in the same manner records are digitized at other Presidential Libraries as part of the FOIA review and access process. Digitization of these processed records will occur after review/notification has been completed. The paper records will continue to be preserved as permanent records after digitization is complete.
Following digitization, NARA will store and preserve the original records and the Obama administration artifacts in an existing NARA facility that meets NARA’s standards for archival storage. The dedicated staff at that location will be responsible for caring for the records and artifacts. Currently, the Obama administration materials are housed in a temporary facility in Hoffman Estates, IL, which is not open to the public.
Obama Presidential records are administered in accordance with the requirements of the Presidential Records Act (PRA) and became subject to public Freedom of Information Act (FOIA) requests on January 20, 2022. NARA is committed to meeting all our obligations under the PRA and FOIA. The digitization and Presidential records review processes are separate and distinct.
About the project
Migrating a website from Drupal 7 to Drupal 9 is a significant undertaking, and the goals and anticipated outcomes of such a migration can vary depending on the specific needs of the website and its stakeholders. However, some common anticipated goals and outcomes of migrating a website from Drupal 7 to Drupal 9 include:
Improved security: Drupal 9 has significant security improvements over Drupal 7, such as better password encryption and protection against SQL injection attacks. Migrating to Drupal 9 can help ensure that the website is more secure and less vulnerable to cyber attacks.
Better performance: Drupal 9 has improved performance over Drupal 7, thanks to its use of newer technologies and frameworks. This means that a website migrated to Drupal 9 may be faster and more responsive than its Drupal 7 counterpart, leading to a better user experience.
Future-proofing: Drupal 7 is approaching its end of life, and will no longer receive official support after November 2022. By migrating to Drupal 9, website owners can ensure that their website remains supported and updated for years to come, reducing the risk of technical debt and compatibility issues.
Easier maintenance: Drupal 9 has a streamlined architecture and improved content editing tools, making it easier for website administrators and content creators to maintain and update the website. This can save time and effort, and reduce the need for technical support.
Improved accessibility: Drupal 9 includes accessibility improvements, such as improved keyboard navigation and support for ARIA attributes, which can help ensure that the website is accessible to all users, including those with disabilities.
Overall, migrating a website from Drupal 7 to Drupal 9 can offer significant benefits in terms of security, performance, future-proofing, maintenance, and accessibility. However, the migration process can be complex and time-consuming, and should be carefully planned and executed to ensure a successful outcome.
Why Drupal was chosen
The federal government likes the Drupal web content management system for several reasons:
- Security: Drupal is known for its robust security features and has a dedicated security team that monitors and addresses security vulnerabilities. This is particularly important for federal government agencies that handle sensitive and confidential information.
- Flexibility: Drupal is a highly flexible and customizable platform that can be tailored to meet the unique needs and requirements of federal government agencies. Drupal's modular architecture allows for the easy integration of third-party tools and services, making it a versatile platform for complex web applications.
- Accessibility: Drupal is built with accessibility in mind and is designed to meet the requirements of Section 508 and the Americans with Disabilities Act (ADA). This is particularly important for federal government agencies that must ensure that their websites are accessible to all users, including those with disabilities.
- Open source: Drupal is an open-source platform, which means that it is freely available and can be modified and distributed by anyone. This makes it an attractive option for federal government agencies that prioritize transparency, collaboration, and cost-effectiveness.
- Large user community: Drupal has a large and active user community, including government agencies, developers, and vendors. This community provides a wealth of resources, including modules, themes, and documentation, making it easier for federal government agencies to develop and maintain their Drupal-based websites.
Overall, the federal government likes Drupal because it is a secure, flexible, accessible, open-source platform with a large and active user community. These factors make Drupal an attractive option for federal government agencies that require a reliable and customizable web content management system.
Technical Specifications
Drupal version:
