Capacity Building Activities

Semi-Structured Interviews

EaaSI Scenarios for Use & Access asks each Node Host to brainstorm scenarios for use and access they believe will drive the adoption of EaaSI; identify users whose use cases they believe may correspond with the scenarios for use and access that they articulated; and ask participants to complete a questionnaire. Node Hosts then analyze participant responses to determine the distance between their participant reflections and the scenarios for use and access driving their interest in software curation, preservation and emulation.

Each Node Host Team was asking to provide 250 words or so that addressed the following questions:

+ Why is software preservation important?
+ What are the advantages to community infrastructure or approaching software + preservation and emulation as a collective action problem?
+ What are your strongest use cases for emulation?
+ What are you hoping to learn through your participation in the EaaSI Network?

Statement of Importance for Software Preservation

Scenarios for (Re)Use & Access

EaaSI Scenarios for Use & Access asks each Node Host to brainstorm scenarios for use and access they believe will drive the adoption of EaaSI; identify users whose use cases they believe may correspond with the scenarios for use and access that they articulated; and ask participants to complete a questionnaire. Node Hosts then analyze participant responses to determine the distance between their participant reflections and the scenarios for use and access driving their interest in software curation, preservation and emulation.

EaaSI Software and Collections Inventory is what is sometimes referred to as a Random (or spot) inventory. Random (or spot) inventories are extremely limited in scope. They are primarily used to verify the location of a representative sampling of objects. They are often completed on a regular basis after a full inventory has been completed to ensure that a more thorough inventory does not need to be completed – however, EaaSI Node Hosts were asked to perform a software & collections inventory as a means of understanding which additional organizational roles are crucial for understanding the software landscape and to identify gaps in collection development and descriptive practice that need to be addressed as part of their participation in EaaSI.

Software & Collections Inventory

In-Person Meeting Exercises

EaaSI Node Leads convened in November 2018 to review the EaaSI beta implementation process, discuss service design for emulation in local organizational contexts, prioritize project activities and review the Participation Agreement drafted in partnership with the Harvard Law School Cyberlaw Clinic.

Training Modules

Stay tuned! 

Our first training modules will address metadata for software preservation and emulation, specially Wikidata for Digital Preservation and the EaaSI Metadata Application Profile. These modules will be posted in early 2019.

Technical Documentation

Stay tuned! 

EaaSI development documentation will be managed using GitLab. Links to the EaaSI GitLab pages will be posted here in early 2019.

Workflows

Stay tuned! 

Some EaaSI workflow documentation will be managed in GitLab. Other workflow documentation, such as workflows developed by Node Host institutions, may be posted to EaaSI GitLab pages, or may be hosted on this website. Links to EaaSI workflow documentation, regardless of location, will be provided here.