About UAiR

Before we run off, braggin' about ourselves, let's get some prominent links up front.

• Project List
• UAiR History
• UA Institutional Repository Copyright Statement
• Privacy Statement

The University of Arizona Institutional Repository (UAiR) was officially born on December 27, 2007, following two years of planning and preparation and four months of development and testing. Originally named the “Digital Commons,” the name was changed in October 2008 to UAiR, as indicated above.

UAiR is an institutional repository and nexus of digital media from contributors from within and without the University. Through the coming months and years, UAiR will expose many of UA's and UAL's papers, journals, research results, and collections, allowing collaborators of UA and UAL projects to leverage the benefits and exposure made possible through UAiR.

Individuals and institutions interested in collaborative efforts, federation, or other involvement should contact UAiR.

Want to know when a collection was added or possibly what's on the horizon for UAiR? Check out the Project List.

If you're interested in the technical and/or chronological history of UAiR, including the plans for the foreseeable future, visit the UAiR History page.

All web pages, supporting technical documents, code, etc, within the Digital Commons portal are, unless otherwise noted, © 2007-2008 The Arizona Board of Regents (ABOR) in compliance with University of Arizona and University of Arizona Libraries policies. For inquiries regarding issues of copyright, contact UAiR.

The UAiR is by nature a repository of descriptive information about digital resources that are owned, stored, and maintained on a distributed basis. Unless otherwise noted, copyright of content should be assumed to be held by the contributor. For questions about the ownership of any individual work, contact UAiR.

Please read the full UAiR Copyright Statement.

UAiR respects its users' right to privacy. For detailed information about information that may be collected and how it may be used, please refer to our Privacy Statement.