I have co-created this list with Michael Ullyot (University of Calgary).
- What kind of resource is it? Is it a digital edition? (If yes, what kind of edition? Critical? Performance? Old-spelling?) Is it a text repository? A database? (If it’s a database, what’s the nature of the data contained therein?)
- How does it complement other digital resources in the same category?
- Is it peer reviewed? If yes, how? As a whole, or as components?
Users and Usability
- Has the resource been designed with different user categories in mind?
- Do its affordances and decisions meet the needs of the users identified by the project as its intended users? If the project does not identify an intended user group, for whom does the project appear to be intended?
- Does it make the affordances or capabilities of the resource obvious, or do they require a lot of digging and tweaking? In other words, how steep is the learning curve for users?
- Is the interface intuitive?
- What does the interface privilege?
- If the resource is an edition, what kind of argument does the interface make about the text? How well does that argument align with the paratextual claims about the editorial approach?
- What does the interface look like (design, colour scheme, mise-en-digital-page)?
- Has the resource met accessibility standards?
- Does the project team clearly document who was responsible for what
- How (and how thoroughly) does the resource document its history, underlying technologies, editorial praxis, encoding standards, metadata model, and revision history?
- Does it offer any guidance on use cases?
- Is the project open-access?
- Is it open-code?
- Is the documentation open-access?
- Is its data exportable in any way? In what formats?
- Does the project follow ISO standards?
- Does it have a data management and preservation plan?
- On what does the resource’s legacy depend?
- Is the resource interoperable with other projects? (E.g., has it planned for linked open data?)