This spreadsheet template was used for collective ideation within the retroTECH team. There are five tabs in the spreadsheet: Guiding Question Stakeholder Roles & Definitions User Stories: Priority, Stakeholder Role, “I want to”, “so that”, Categories, Relationship to other work …Continue Georgia Tech: User Stories Spreadsheet
This image provides a snapshot of user story development and prioritization by the team within the retroTECH Online ZenHub account. Because retroTECH Online was partially a software development effort, it was helpful to apply an agile project management framework towards …Continue Georgia Tech: User Stories in Zenhub Snapshot
This matrix corresponds to the ARL Code of Best Practices for Software Preservation and the Software Stories that were developed as part of retroTECH Online. The “Situations” listed in the matrix correspond to the five situations or scenarios in the …Continue Georgia Tech: Review of the ARL Code of Best Practices
This checklist to help the project team identify which pieces of software they want to include in their pilot project.
This spreadsheet is used to capture input or metadata fields from several other assets where information about software or file formats is captured. The intent is that this document can be used to analyze common fields found within the various …Continue University of Illinois Metadata Capture Locations
Document providing some additional explanation on metadata fields found within the 2019_softwareCollection_Inventory_WorkingCopy.xlsx spreadsheet. Software spreadsheet may have evolved since writing.
This spreadsheet was developed by FCoP, and completed by the University of Illinois cohort team. It contains metadata fields established by cohort leaders.
Project plan for managing the Hembrough software collection donation. The plan is divided into four stages, and includes metadata and rationale for choices made in metadata capture and spreadsheet organization. This is a reference document.
Example of a spreadsheet used to capture metadata about software titles. Content is primarily from the Hemborough software donation collection stewarded by Digital Preservation Services.
Template for creating a README file to include in a software preservation submission information package.
This document is intended to serve as a master workflow for software preservation practice at the University of Illinois. It outlines the major task categories of acquiring, cataloging, structuring, imaging, quality assurance (QA)/quality control (QC) testing and ingesting the software …Continue University of Illinois Software Preservation Procedures Workflow
This fillable spreadsheet assists end-users in planning and documenting an install workflow.
This document assists end-users in navigating the Digital Content Format Registry. This is intended for those who want to review the registry entries. The Digital Content Format Registry is open to the public – no login is required. Authentication is …Continue University of Illinois Digital Content Format Registry
This document identifies three classes of digital curation action events (media reformatting, software acquisition, digital content format research request) and next steps to starting the curation action.