The following user profile guidance is inspired by the AIAAIC - User guide . The AIAAIC database and Wiki knowledge graph is an independent, open access resource on ‘AI, Algorithmic and Automation Incidents and Controversies’.
The Environmental Impact of AI (EAI) is an open access database created by undergraduate students to provide publicly accessible guidance and sources addressing the environmental impact of artificial intelligence systems.
The database runs through Google Sheets and has an accompanying resource on Google Sites which includes a methodology explainer, user guide and link to the database. The EAI database is easily accessible through internet access and is aimed towards a broad range of audiences. This series of user profiles guides researchers on potential users of the database.
This resource is created by undergraduate students with students in mind with its easily accessible interface and collection of journal articles and academic papers. Students of a variety of ages wishing to conduct their own projects or research on AI, sustainability and climate impact would likely find this a useful resource.
A broader category of users – beyond purely academic researchers – this group may enjoy the format of this resource which is easy to navigate and to specify key terminology. This may be used for wide or more nuanced research.
Academic papers and journal articles, most published in the last five years, make up a significant proportion of the database.
This resource presents up to date information on the latest research and innovation surrounding AI technology and sustainability making it a valuable resource for industry professionals.
As AI is a growing public interest and concern, this date base aids researchers within governments and think tank groups interested in the environmental impact of AI across a variety of categories. These include water usage, land use, the extraction of finite resources and rare materials as well as carbon emissions and energy consumption. The global aspect of this database also allows for an international approach.
The site and database offer statistics, research and other news coverage opinion pieces on the environmental impact of AI which could inform and interest journalists researching and writing on the subject.
This resource offers a starting point for those creating educational and public information content. Entries in the database go through thorough fact checking and review before entering the database.
This resource is build with the public in mind and its building process has been entirely focused on transparency and accessibility to a range of audiences.
Finally, this resource aims to work to the benefit of non-profit organisations and campaign groups by collaborating scientific research and non-partisan perspectives. This resource with its easy to sort function allows groups to identify key campaigns.
The EAI database is built and guided by five core objectives and values:
- Accessibility (users can access information in database)
- Usability (users can navigate the database)
- Retrievability (users can go to the source of material in database)
- Interpretability (users can make sense of database entries)
- Transparency (users can understand reason for database entries)
The database resides within one format on Google Sheets with guidance within the Methodology guidance and User guidance as well as a Glossary for acronyms and specific language. DOI links are provided when available to allow the resource to continue to function best when as website domains shift.
Sources within the database are broken down into numerous categories allowing for easy filtering by users. These categories include technology type, industry funding and cost of impact.
The database is built with minimal bias and consistent discussion between designers to ensure continuity between database entries and sources. However, human error and website updates or link changes are possible.
Research on the environmental impact of AI is an often divided and continually developing subject meaning sources in the database will need continual updating as the project ages.