Lots of folx have already mentioned things the IFTF is has done and continues to do.
There are two other larger collections I am in communication with as part of my own preservation efforts. The first is Consortium on Electronic Literature (CELL), which has been trying to import existing metadata on works as part of the Wikidata project (and as found on Wikipedia, among other services). The second is The NEXT, which is a smaller collection but has made great progress toward emulated systems and configurations for older electronic literature of all sorts.
Are there any major issues being faced that I could look into tackling as part of a thesis or independent study course? I come from a computer science background, so I would be looking for technical challenges that I could potentially help with.
Major challenges include, but are not limited to, the following:
Platforms
- Death (i.e., the death of Flash for early online works).
- API changes (i.e., what happens when the Facebook API changes and older games don’t work any more.)
- Policy changes (i.e., Steam and Itch’s removal of “adult games”)
Preservation and Access
- What does it mean to play older works? Should hardware controls be emulated or re-constructed? Should “lag” be programmed into emulated systems to mimic older access requirements and processes?
- What does it mean to save distributed works? Some older MMOs have now died, and the stories that existed within those might not be recoverable. The same, too, with stories across social media platforms. Trying to preserve what it means to access, for example, for electronic literature across TikTok or Twitter posts when those platforms change is now a problem.
- What does it mean to save configurations? Some older visual novels only work on Windows 98. Some only work on Windows XP. These versions are no longer maintained by Microsoft. What does it mean to have virtual systems of different, older operating systems to still play games only designed for them?
Metadata
Something I have been working on this past summer was trying to identify where the larger, funded collection aligns on fields. For example, The NEXT has a comprehensive set of fields that cover accessibility concerns (json-elms/schema/schema.md at main · videlais/json-elms · GitHub) that others could also implement or add as optional fields.
A major challenge, in my conversations with people from The NEXT and CELL, is in just trying to figure out what metadata to save or maintain and how to get different databases to communicate with each other.
Traversals
As part of efforts about the Electronic Literature Collection, traversals of older works has become a growing concern. Myself, among other people, have been trying to capture video and audio recordings of works to save them along with metadata about the work. This has become a renewed effort as platforms like Steam and Itch are forced to remove works that may or may not be saved anywhere else.