ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
 Now (2016)Year 1 (2017)Year 2 (2018)Year 3 (2019)Year 4 (2020)Year 5 (2021)Year 6 (2022)
2
Coordination/Governance/Reporting1) Establish a working group structure 1) Establish a community-endorsed coordinating body for this work 1) Hire a part-time or full-time program coordinator
3
2) Create current list of all concurrent, grant-funded software preservation proposals and programs: PERSIST, Software Heritage and SSI2) Begin work on funding proposals/parallel tacks for accomplishing different aspects of the work2) Formalize working groups into committees
4
3) Establish working group leads/facilitators
5
4) Establish a reporting mechanism for sharing updates across working groups
6
5) Establish a shared documentation repository (GitHub, etc.)
7
Research/Scoping1) Establish a body of use cases 1) Review and consolidate inventories for existing software collections 1) Expand the inventory of existing software collections to research necessary dependencies for that software1) Design a study that can be modified and deployed across institutions to evaluate reuse cases for software preservation outside of staff
8
2) Review and Document Platforms for Accessing Archived Software (partially completed - David Rosenthal's report)2) Create an evaluation/survey tool that helps insitutions to document the frequency of file formats existing in their collections - towards beginning to prioritize collecting across LAMs
9
Outreach/Advocacy/Training1) Define the value of software preservation - create a software preservation manifesto that can be used to create a community vocabulary and baseline - solicit signatures, first step towards raising the visibility 1) Begin work on the "advocacy toolkit" with modules for each of the top 3 major stakeholder groups identified from the body of use cases 1) Continue work on advocacy toolkit, consider expanding from 'the case for local support' to 'soliciting allies from complementary communities of practice' 1) Start creating an Emulation Training Series/Workshop for archivist/librarian/curator audiences based on the documentation created from the 2-3 willing volunteers - Identify existing platforms or organizations that would be interested in sponsoring the training
10
2) Create a "basic guide to software preservation" with lit review, studies/resources, contacts for existing projects and glossary - towards an "advocacy toolkit"2) Start work on a strategy for pursuing partnerships with the software industry - articulating the different collection and use goals (software they are phasing out, current software they serve up from the cloud, etc.) 2) Continue strategy for pursuing relationships with the software industry - identify 2-3 specific strategies for local insitutions [Ex. alumni networks/working with your development office; asking to present at an industry event; locating all of our colleagues that work in corporate archive settings to identify ways to align with corporate responsibility initiatives]
11
3) Identify 2-3 volunteers that are willing to learn and document their experience installing, running and planning out a workflow/integrations with EaaS
12
Policies/Standards1) Gather up, annotate and publish existing accessioning/donor agreement templates for accessioning software1) Begin exploring the question of "what is different about software" and determine if there is already a "common core" for software across descriptive, technical and administrative facets; if more common core work is needed, begin that work 1) Continue work on templates for collection development policies and donor agreement guides for collection software
13
2) Identify any existing collection development policy language that mentions software2) Centralize and share existing schema and controlled vocabularies for describing software 2) Continue work on metadata best practices for software and associated dependencies
14
3) Establish working group contact with ACM standards working groups and others that may be further down the road in this work 3) Reseach ILL as an existing system that could include software for locally hosted or centrally hosted emulation environments
15
4) Begin to establish technical standards for packaging the components of an emulation environment
16
Preservation/Curation-Ready Software Development1) Gather resources/past efforts and standards for incorporating preservation or curation-friendly features into current software development projects 1) Define the scope of preservation/curation-ready development use cases: digital scholarship projects in the libary, research software, etc 1) Identify 2-3 volunteer organizations willing to serve as test beds for phased implementation of curation-ready development for a different use case 1) Begin iterative testing of curation-ready software development by introducing one or two new work steps/processes into volunteer organizations existing workflows
17
2) Research existing funding agency requirements that imply a need for best practices guide2) Draft language about curation/preservation-ready-software for a data management plan2) Start documenting existing software development workflows for each of the major curation-ready software use cases; possibly talk-aloud type study (this documentation would include type of version control system used by developers, commenting and function/script naming practices, etc.)
18
Technical infrastructure1) Research resources needed to host and maintain a community EaaS sandbox 1) Begin work on a clearninghouse/federated registry to enable discovery of software - research feasibility of existing library catalogs or consortial discovery points; 1) Explore explicit connections between EaaS sandbox and more than one software repository 1) Identify backend barriers to offer "seamless" emulation experience/user interface
19
2) Identify partners interested in piloting a private LOCKSS network for software titles2) Test and document pathways to apply droid/jhove --> identify formats --> render file formats within and without EaaS; 2) Create a proof-of-concept automated workflow that would allow organizations with digital repositories to send one copy of the software image or source code (and any associated metadata) into their repository and one copy to either the PLN or a centralized access repository
20
3) Beginning research on ways to integrate EaaS with existing repository and course mangement software
21
Rights Management/Agreements1) Establish legal and policy partners for pursuing software rights management in a consortial setting 1) Document and publish existing rights holder agreements within software collecting organizations
22
2) Establish MOU between institutions sharing a PLN or software repository
23
3) Create a body of existing best practice guides that can be used for future development of software preservation best practice guide
24
4) Begin working with legal and policy partners to develop Fair Use Best Practices Guide for Software Preservation
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100