mirror of
https://github.com/UW-CALMA/datarescue.git
synced 2025-02-20 08:41:31 -08:00
generalized Gitbook for non-UW audiences
This commit is contained in:
Brandon Locke
parent
df30f6c467
commit
3a4fc99049
12 changed files with 110 additions and 76 deletions
41
README.md
41
README.md
|
|
@ -5,14 +5,12 @@ description: READ ME FIRST! ⛵
|
|||
# 🛟 Data Rescues 2025
|
||||
|
||||
{% hint style="info" %}
|
||||
As of January 24, 2025 we are NOT actively accepting contributions to our internal forms. Please continue reading for information on how to submit records to existing ongoing projects. Also, check out the [Updates page](resources-and-tools/updates.md) for more recent-ish information.
|
||||
This Gitbook is an information resource and customizable template for Data Rescue events. It was [first developed by BKS Studio, LLC](https://github.com/nguyen-info/datarescue) in collaboration with the [University of Washington Center for Advances in Libraries, Museums, and Archives (CALMA)](https://calma.ischool.uw.edu/) for Data Rescue events in Seattle in January 2025 and is available for remix and reuse under a [Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-nc-sa/4.0/) license.
|
||||
|
||||
If you are organizing a Data Rescue event, see the [For Organizers](resources-and-tools/for-organizers.md) page for more information about using this resource and planning an event.
|
||||
{% endhint %}
|
||||
|
||||
In response to political threats to social, environmental, health, and personal data, the [University of Washington Center for Advances in Libraries, Museums, and Archives (CALMA)](https://calma.ischool.uw.edu/) in collaboration with Seattle-based BKS Studio, is hosting a series of DATA RESCUE efforts. If you are also concerned about losing access to vital public government data and files, you are in the right place!
|
||||
|
||||
Modeled after the 2016-2017 DataRescue movement that responded to hostile conditions towards environmental and climate science data, these ad hoc digital archiving volunteer events invite community members to apply their technical skills and social values in response to new threats to important data. While Data Rescues can focus on any type of at-risk public and government data, many have focused on environmental issues given[ documented threats and modifications](https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0246450) by recent political agendas. 
|
||||
|
||||
This Gitbook is a knowledge base for the 2025 Seattle-based Data Rescues events. Open to public suggestions and contributions, this is a living document that is created and informed by documentation and literature from the 2017-2018 Data Rescues and by community-informed brainstorming discussions. 
|
||||
Modeled after the 2016-2017 DataRescue movement that responded to hostile conditions towards environmental and climate science data, these ad hoc digital archiving volunteer events invite community members to apply their technical skills and social values in response to new threats to important data. While Data Rescues can focus on any type of at-risk public and government data, many have focused on environmental issues given[documented threats and modifications](https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0246450) by recent political agendas. Open to public suggestions and contributions, this is a living document that is created and informed by documentation and literature from the 2017-2018 Data Rescues and by community-informed brainstorming discussions. 
|
||||
|
||||
The following Gitbook pages include:
|
||||
|
||||
|
|
@ -20,9 +18,10 @@ The following Gitbook pages include:
|
|||
* Guide on [How To Start](how-to-start/) contributing to Data Rescues goals
|
||||
* Detailed instructions on contributing to Data Rescue track tasks ([communication](how-to-start/track-1-communications.md), [assessment](how-to-start/track-2-data-assessment.md), [technical](how-to-start/track-3-technical.md))
|
||||
* A growing list of [Learning Resources](resources-and-tools/) (readings and tools)
|
||||
* [Updates page](resources-and-tools/updates.md) for information about other projects going on right now
|
||||
* [Contact information](stay-in-touch.md) to connect with other relevant networks and communities
|
||||
|
||||
You are invited to comment and suggest ideas and updates to this site. **Submit Change Requests** through the Data Rescue GitHub repository at: [https://github.com/nguyen-info/datarescue/tree/main](https://github.com/nguyen-info/datarescue/tree/main)
|
||||
You are invited to comment and suggest ideas and updates to this site. **Submit Change Requests** through the Data Rescue GitHub repository at: [https://github.com/UW-CALMA/datarescue](https://github.com/UW-CALMA/datarescue).
|
||||
|
||||
***
|
||||
|
||||
|
|
@ -30,37 +29,11 @@ You are invited to comment and suggest ideas and updates to this site. **Submit
|
|||
|
||||
🐣 **I’m new to Data Rescues** → Read a bit more about the [background](what-are-data-rescues.md) to understand why, when, where, how on this movement
|
||||
|
||||
💻 **I’ve rescued data before** → First, look through our [Collecting Scope](collecting-scope.md) page for the Seattle Data Rescues vision then move to contribute to community efforts
|
||||
💻 **I’ve rescued data before** → First, look through our [Collecting Scope](collecting-scope.md) page for the Data Rescue's vision then move to contribute to community efforts
|
||||
|
||||
***
|
||||
|
||||
### Frequently Asked Questions - FAQs 🛶
|
||||
|
||||
Q: I am not feeling well, will you provide basic PPE (masks/sanitizing wipes)?
|
||||
|
||||
A: This is a mask-friendly event, and we encourage attendees to bring and wear masks for added protection against COVID-19. We encourage everyone who might feel under the weather to either attend via zoom OR come to the next Data Rescue event (if condition improves).
|
||||
|
||||
#### Q: What devices or equipment do I need to bring?
|
||||
|
||||
A: This is a BYOD (Bring Your Own Device) sort of event meaning participants are invited to bring along whatever devices they might need to contribute their skills. If this means just a pen and paper, that’ll do! NOTE: we do have a limited supply of laptops in case yours goes on the fritz last minute.
|
||||
|
||||
#### Q: How much programming or technical skills does a participant need?
|
||||
|
||||
A: For these Data Rescues, we only require surface level understanding of technology meaning do you know key differences between a physical and digital, do you have basic computer skills or have an interest in developing more, and can you understand the core threats to digital files like deletion and corruption?
|
||||
|
||||
#### Q: Is there anything I need to read or review in preparation for the event?
|
||||
|
||||
A: There is no required reading prior to attending the event, but you are welcomed to explore our [Gitbook documentation](https://community-archives.gitbook.io/data-rescue-2025) that shows suggested tasks, some potential readings, and overall information on the event structure.
|
||||
|
||||
#### Q: Do I need to be there the entire time?
|
||||
|
||||
A: No, these Data Rescue events are set up as Drop-Ins where most people can complete a digital preservation task within the hour. No one is expected to stay beyond that or arrive right at the start of the event. 
|
||||
|
||||
#### Q: Can I bring a friend?
|
||||
|
||||
A: Yes, friends and family (all ages) are welcome but please note that we are limited in in-person space. If more people arrive than we anticipated, we may ask you and your guest to move to our overflow spaces (both online or in-person). You are also welcomed to invite your friend to attend the next Data Rescue event.
|
||||
|
||||
Contact [calma@uw.edu](mailto:calma@uw.edu) for questions and/or more information. 
|
||||
|
||||
\
|
||||
|
||||
|
|
|
|||
|
|
@ -13,4 +13,5 @@
|
|||
* [Readings](resources-and-tools/readings.md)
|
||||
* [Model Projects](resources-and-tools/relevant-projects.md)
|
||||
* [Updates](resources-and-tools/updates.md)
|
||||
* [For Organizers](resources-and-tools/for-organizers.md)
|
||||
* [🙋 Stay in Touch](stay-in-touch.md)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,10 @@
|
|||
description: What are we collecting? Why?
|
||||
---
|
||||
|
||||
{% hint style="info" %}
|
||||
This is an example of the Collecting Scope used for the Seattle Data Rescue. Customize as desired.
|
||||
{% endhint %}
|
||||
|
||||
# 🗃️ Collecting Scope
|
||||
|
||||
**Seattle Data Rescue Suggested Collection Criteria**\
|
||||
|
|
|
|||
|
|
@ -4,6 +4,10 @@ description: READ BEFORE STARTING YOUR CONTRIBUTION
|
|||
|
||||
# 🙏 Community Agreements
|
||||
|
||||
{% hint style="info" %}
|
||||
This is an example of the Community Agreements used for the Seattle Data Rescue. Customize as desired.
|
||||
{% endhint %}
|
||||
|
||||
At Data Rescue events, we strive to support and create an environment that encourages all participants—organizers, supporters, any and all stakeholders to hold safe, engaging, and respectful environments where each person is able to focus as much of their energy on the Data Rescue’s intent.
|
||||
|
||||
These are our suggested community agreements for all Data Rescue event as designed by the Collective Responsibility: [Code of Conduct and Community Agreement – Collective Responsibility](https://laborforum.diglib.org/code-of-conduct-and-community-agreement/). We ask all volunteers to help uphold these community practices and principles. 
|
||||
|
|
|
|||
|
|
@ -4,9 +4,6 @@ description: Step-by-step instructions
|
|||
|
||||
# ⭐ How To Start
|
||||
|
||||
{% hint style="info" %}
|
||||
As of January 24, 2025 we are NOT actively accepting contributions to our internal forms. Please continue reading for information on how to submit records to existing ongoing projects.
|
||||
{% endhint %}
|
||||
|
||||
Hello & welcome!
|
||||
|
||||
|
|
@ -16,14 +13,14 @@ Whether you are just now thinking about responding to current data risks and thr
|
|||
|
||||
Now that you’ve reviewed the general expectations and background information, we ask all volunteers to following these steps to start:
|
||||
|
||||
1. Read the [community agreements](../) page. 
|
||||
1. Read the [community agreements](../community-agreements.md) page. 
|
||||
2. Review track summaries (below) to pick a path. 
|
||||
3. Navigate to the track Gitbook page (see sidebar drop down or below links), 
|
||||
4. Pick 1 task on the ones listed on your select track to begin (some may require installing tools)
|
||||
5. Follow instructions for selected task under the "workflow" header to complete the task
|
||||
6. Work on your selected task (ask for clarification or help from Coordinators)
|
||||
7. REPEAT steps 2-6 if you want to take on another task (or go to the LAST STEP to say bye)👋🏼 
|
||||
8. Submit an exit ticket (summary of all your work) using this [form](https://docs.google.com/forms/d/e/1FAIpQLSdTiK6Y6VZCgM7vZg4Mj3PDUIyxeKxecHOUzqcOtGh6AmbnCw/viewform?usp=header)
|
||||
8. Submit an exit ticket (summary of all your work) using this form [**link to Work Completion Status Form**]
|
||||
|
||||
### Track List Options
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,6 @@
|
|||
# 🎙️ Track 1 (Communications)
|
||||
|
||||
{% hint style="info" %}
|
||||
As of January 24, 2025 we are NOT actively accepting contributions to our internal forms. Please continue reading for information on how to submit records to existing ongoing projects.
|
||||
{% endhint %}
|
||||
|
||||
This track focuses on creating, revising, and sharing information about at-risk data. This includes adding context about collected data in order to improve management and findability of data for future purposes. The below are our initial goals coming from CALMA / Seattle-based efforts, but all participants are free to suggest and pursue other contributions.
|
||||
This track focuses on creating, revising, and sharing information about at-risk data. This includes adding context about collected data in order to improve management and findability of data for future purposes.
|
||||
|
||||
**Tech Skill Level:** Beginner
|
||||
|
||||
|
|
@ -37,7 +33,7 @@ This track focuses on creating, revising, and sharing information about at-risk
|
|||
|
||||
🗂️**Workflow**
|
||||
|
||||
1. Review the Digital Research Repository outreach template ([Download copy](https://docs.google.com/document/d/1OjEUMV00Kn1axqIBUlt44tFYCOSKDhIQXZzG8J3xIas/edit?usp=sharing) via this link)
|
||||
1. Review the Digital Research Repository outreach template ([See example from Seattle Data Rescue](https://docs.google.com/document/d/1OjEUMV00Kn1axqIBUlt44tFYCOSKDhIQXZzG8J3xIas/edit?usp=sharing) via this link)
|
||||
2. Find a researcher (& contact information) that you believe is conducting research in an area of significance.
|
||||
3. Customize template with your recipient's basic info (name, their area of focus like Climate Science or Environmental changes, ideas for what to deposit, and how it might benefit the researcher and/or their audiences)
|
||||
4. Send/distribute outreach message to selected recipient.
|
||||
|
|
@ -60,7 +56,7 @@ This track focuses on creating, revising, and sharing information about at-risk
|
|||
3. What other legislation exists that deals with preservation of at-risk data (USA or beyond)?
|
||||
4. How does the American public perceive government data loss? 
|
||||
5. How does this compare with other countries?
|
||||
4. Write a paragraph on your findings, reflections, or lingering questions onto the shared research google doc: [https://docs.google.com/document/d/1BH24Ks63J55K1jFmdUxUKubuqusCAxwU-9verrfjTbc/edit?usp=sharing](https://docs.google.com/document/d/1BH24Ks63J55K1jFmdUxUKubuqusCAxwU-9verrfjTbc/edit?usp=sharing)
|
||||
4. Write a paragraph on your findings, reflections, or lingering questions onto the shared research google doc: [**Link to Research Team Summaries**]
|
||||
|
||||
🛠️**Skills Needed:** Basic command of English to either read or write summaries of findings. Intermediate to advanced levels of reading and writing in order to find, assess, and summarize findings for a general United States audience and English reader. Additional language skills would be useful for translation or finding global readings and data. 
|
||||
|
||||
|
|
@ -76,7 +72,7 @@ This track focuses on creating, revising, and sharing information about at-risk
|
|||
3. Are people on social media commenting on these removals?
|
||||
4. Are there back up copies on sites like the [Internet Archive](http://web.archive.org/), [End of Term](https://eotarchive.org/data/), [DataLumos](https://www.datalumos.org/datalumos/search/studies)? 
|
||||
5. How do these tactics of removing public federal information compare with other countries?
|
||||
* Write a paragraph on your findings, reflections, or lingering questions onto the shared research google doc: [https://docs.google.com/document/d/1BH24Ks63J55K1jFmdUxUKubuqusCAxwU-9verrfjTbc/edit?usp=sharing](https://docs.google.com/document/d/1BH24Ks63J55K1jFmdUxUKubuqusCAxwU-9verrfjTbc/edit?usp=sharing)
|
||||
* Write a paragraph on your findings, reflections, or lingering questions onto the shared research google doc: [**Link to Research Team Summaries**]
|
||||
|
||||
#### <mark style="background-color:purple;">4. Create promotional text/images</mark>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,6 @@
|
|||
# 🔍 Track 2 (Data Assessment)
|
||||
|
||||
{% hint style="info" %}
|
||||
As of January 24, 2025 we are NOT actively accepting contributions to our internal forms. Please continue reading for information on how to submit records to existing ongoing projects.
|
||||
{% endhint %}
|
||||
|
||||
This track focuses on finding and evaluating valuable and relevant at-risk data.This helps others be able to complete capturing tasks as they can depend on your “peer reviewed” assessment.
|
||||
This track focuses on finding and evaluating valuable and relevant at-risk data. This helps others be able to complete capturing tasks as they can depend on your “peer reviewed” assessment.
|
||||
|
||||
**Tech Skill Level:** Intermediate
|
||||
|
||||
|
|
@ -41,11 +37,10 @@ This track focuses on finding and evaluating valuable and relevant at-risk data.
|
|||
* Review established collecting criteria to see if the webpage/website/dataset falls within this Data Rescue scope
|
||||
* NOTE: suggestions will be captured and/or deposited to 1 of the following repositories 
|
||||
* [End of Term](https://eotarchive.org/) (EoT) : Mostly includes and collects webpages and files related to specific presidential administrations
|
||||
* [UW Web Archives](https://archive-it.org/organizations/729): More focused on Northwest regional history, University of Washington related work and studies, and labor relations
|
||||
*  [Internet Archive](https://archive.org/about/): more broad collecting scope. Tends to capture web content (meaning webpages or part of websites) Harder to upload actual files. 
|
||||
* Research, name, and document web pages (individual pages or a small batch of pages within a website. 
|
||||
* For a large quantity of web pages or complex large websites, see Track 3.
|
||||
* Submit basic information about the web page on [this Data Tracking Form](https://docs.google.com/forms/d/e/1FAIpQLSfII-rl4yUcGPJlPWk9knWMhC_qBueJLEPcC7vphPeVisLhHA/viewform?usp=sf_link). 
|
||||
* Submit basic information about the web page on this Data Tracking Form [**Link to Data Tracking Form**]. 
|
||||
|
||||
🛠️**Skills Needed:** Be able to browse through web pages to assess value or significance of content then be able to access a google form to submit assessment and basic metadata (details about the webpage/website)
|
||||
|
||||
|
|
@ -56,7 +51,7 @@ This track focuses on finding and evaluating valuable and relevant at-risk data.
|
|||
🗂️**Workflow**
|
||||
|
||||
* Read [dublin core basic manual ](https://www.dublincore.org/specifications/dublin-core/usageguide/)to learn about the use of metadata for digital records (for explanation on selected metadata fields, see section 4. Elements)
|
||||
* Navigate to the [Data Tracking List ](https://docs.google.com/spreadsheets/d/1tOS7B3lgK-8wdgyhY81ntfICMIkGwAiHfeV63hi3UzU/edit?usp=sharing)sheet (stay on the first tab “EDIT TO THIS TABLE”) 
|
||||
* Navigate to the [**link to Data Tracking List**] sheet (stay on the first tab “EDIT TO THIS TABLE”) 
|
||||
* Select a row with an item that is marked as "Needs Metadata" (this info found in column K)
|
||||
* Fill-in descriptive text for your select row for all 5 metadata columns (these are columns P through U colored in teal blue)
|
||||
* Use Data Tracking sheet for title and URL to find other information to create description
|
||||
|
|
@ -70,7 +65,7 @@ This track focuses on finding and evaluating valuable and relevant at-risk data.
|
|||
|
||||
🗂️**Workflow:** 
|
||||
|
||||
* Reference this [Data Tracking List - Data Rescue 2025 (Responses)](https://docs.google.com/spreadsheets/d/1tOS7B3lgK-8wdgyhY81ntfICMIkGwAiHfeV63hi3UzU/edit?usp=drive_link) that are ready for archiving
|
||||
* Reference this [**Link to Data Tracking Form**] that are ready for archiving
|
||||
* Select a row
|
||||
* Change row Status to “In-progress - Capture ”
|
||||
* To capture, decide if it goes to the Internet Archive or the End of Term project
|
||||
|
|
@ -88,7 +83,7 @@ This track focuses on finding and evaluating valuable and relevant at-risk data.
|
|||
🗂️ Workflow 
|
||||
|
||||
* Read [Dublin Core basic metadata manual](https://www.dublincore.org/specifications/dublin-core/usageguide/) to learn about the use of metadata for digital records (for explanation on selected metadata fields, see section 4. Elements) 
|
||||
* Navigate to the [Data Tracking List](https://docs.google.com/spreadsheets/d/1tOS7B3lgK-8wdgyhY81ntfICMIkGwAiHfeV63hi3UzU/edit?usp=sharing) sheet (stay on the first tab “EDIT TO THIS TABLE”) 
|
||||
* Navigate to the [**link to Data Tracking List**] sheet (stay on the first tab “EDIT TO THIS TABLE”) 
|
||||
* Select a row with an item that is marked as "Needs Metadata" (this info found in column K) 
|
||||
* Change row status to "In Progress - Metadata" for duration of your description work,
|
||||
* Fill-in descriptive text for your select row for all 5 metadata columns (these are columns O through U colored in teal blue) 
|
||||
|
|
|
|||
|
|
@ -1,8 +1,5 @@
|
|||
# 🕵️ Track 3 (Technical)
|
||||
|
||||
{% hint style="info" %}
|
||||
As of January 24, 2025 we are NOT actively accepting contributions to our internal forms. Please continue reading for information on how to submit records to existing ongoing projects.
|
||||
{% endhint %}
|
||||
|
||||
This track focuses on the actual capture of at-risk data in a variety of formats. As these tasks require the most technical knowledge, skills, and equipment, volunteers are encouraged to take this track when they are able to dedicate more time.
|
||||
|
||||
|
|
@ -44,9 +41,9 @@ This track focuses on the actual capture of at-risk data in a variety of formats
|
|||
2. Download the a monitoring tool like:
|
||||
1. HTTP API tracker [https://github.com/edgi-govdata-archiving/web-monitoring-db](https://github.com/edgi-govdata-archiving/web-monitoring-db) 
|
||||
2. Comprehensive list of other tools here: [https://github.com/edgi-govdata-archiving/awesome-website-change-monitoring](https://github.com/edgi-govdata-archiving/awesome-website-change-monitoring) 
|
||||
3. Identify website to track using [this Data Tracking List](https://docs.google.com/spreadsheets/d/1tOS7B3lgK-8wdgyhY81ntfICMIkGwAiHfeV63hi3UzU/edit?usp=drive_link) 
|
||||
3. Identify website to track using [**link to Data Tracking List**]) 
|
||||
4. Deploy tracker for selected website 
|
||||
5. Submit information about tracked website to [the Data Tracking form](https://docs.google.com/forms/d/e/1FAIpQLSfII-rl4yUcGPJlPWk9knWMhC_qBueJLEPcC7vphPeVisLhHA/viewform?usp=sf_link)
|
||||
5. Submit information about tracked website to [**link to the Data Tracking form**]
|
||||
|
||||
**Skills Needed:** Advanced understanding of software deployment, APIs, and technical git repositories. 
|
||||
|
||||
|
|
@ -56,7 +53,7 @@ This track focuses on the actual capture of at-risk data in a variety of formats
|
|||
|
||||
🗂️**Workflow**
|
||||
|
||||
1. Identify a web file ready to [ready to be captured](https://docs.google.com/spreadsheets/d/1tOS7B3lgK-8wdgyhY81ntfICMIkGwAiHfeV63hi3UzU/edit?usp=sharing)
|
||||
1. Identify a web file ready to ready to be captured [**link to Data Tracking List**]
|
||||
2. Update the "Status" cell that you are working on that row so that others will know that you are working on that web file
|
||||
3. Using web capture software (like [Conifer](https://guide.conifer.rhizome.org/)) pick an at-risk website that includes at-risk data
|
||||
4. Change the status on the same "Status" cell to notify that the web file/data has been archived and to avoid others from doing redundant work
|
||||
|
|
@ -73,10 +70,8 @@ This track focuses on the actual capture of at-risk data in a variety of formats
|
|||
2. Verify that downloadable datasets contain enough descriptive information (data files, interactive maps, etc.) 
|
||||
3. Capture dataset(s) to internal storage (temporary place)
|
||||
4. Submit and upload the dataset(s) via 1 of these options
|
||||
1. FOR UW affiliates ONLY: [https://docs.google.com/forms/d/e/1FAIpQLSfk0pfq4NTxlxAy2cmA3RYVLatn-tMwzv5NljayYvXNv8dp6Q/viewform?usp=sharing](https://docs.google.com/forms/d/e/1FAIpQLSfk0pfq4NTxlxAy2cmA3RYVLatn-tMwzv5NljayYvXNv8dp6Q/viewform?usp=sharing) (URL to Google Drive or UW OneDrive)
|
||||
2. FOR Non-UW Affiliates:
|
||||
* Files up to 2 GB [https://wetransfer.com/](https://wetransfer.com/) Send to [snguye@uw.edu](mailto:snguye@uw.edu) 
|
||||
* OR submit the URL of a downloadable folder via the exit tix [https://bit.ly/datarescue-bye](https://bit.ly/datarescue-bye) 
|
||||
* Files up to 2 GB [https://wetransfer.com/](https://wetransfer.com/) 
|
||||
* OR submit the URL of a downloadable folder via the exit tix [**link to Work Completion Form**] 
|
||||
5. You can delete dataset after successful transfer to Data Rescue coordinators
|
||||
|
||||
🛠️**Skills Needed:** Intermediate understanding of different dataset types and file formats. Comfort with downloading and saving larger files.
|
||||
|
|
@ -93,13 +88,11 @@ This track focuses on the actual capture of at-risk data in a variety of formats
|
|||
* [checksum](https://corz.org/windows/software/checksum/): A file hashing application for Windows, a program that generates and verifies BLAKE2, SHA1 and MD5 hashes (aka. "MD5 Sums", or "digital fingerprints") of a file, a folder, or recursively.
|
||||
* There are a number of other tools, the above mentioned are examples (see Digital Preservation Coalition Digital Preservation Handbook above).
|
||||
* Ask the "data titan" coordinator to gain access to captured files
|
||||
* Use the [dataset tracking list ](https://docs.google.com/spreadsheets/d/1tOS7B3lgK-8wdgyhY81ntfICMIkGwAiHfeV63hi3UzU/edit?usp=drive_link)to check details to create checksum 
|
||||
* Use the [**link to Data Tracking List**] to check details to create checksum 
|
||||
* Run a check on the selected data to create the supplemental checksum value
|
||||
* Upload checksum file using (1 )of the following options
|
||||
* FOR UW affiliates ONLY: [https://docs.google.com/forms/d/e/1FAIpQLSfk0pfq4NTxlxAy2cmA3RYVLatn-tMwzv5NljayYvXNv8dp6Q/viewform?usp=sharing](https://docs.google.com/forms/d/e/1FAIpQLSfk0pfq4NTxlxAy2cmA3RYVLatn-tMwzv5NljayYvXNv8dp6Q/viewform?usp=sharing) (URL to Google Drive or UW OneDrive)
|
||||
* FOR Non-UW Affiliates:
|
||||
* Submit and upload the dataset(s) via 1 of these options
|
||||
* Files up to 2 GB https://wetransfer.com/ Send to snguye@uw.edu 
|
||||
* OR submit the URL of a downloadable folder via the exit tix https://bit.ly/datarescue-bye 
|
||||
* Files up to 2 GB [https://wetransfer.com/](https://wetransfer.com/) 
|
||||
* OR submit the URL of a downloadable folder via the exit tix [**link to Work Completion Form**] 
|
||||
|
||||
🛠️**Skills Needed:** Best for those who have strong tech skills, attention to detail, and willingness to read the docs.
|
||||
|
|
|
|||
68
resources-and-tools/for-organizers.md
Normal file
68
resources-and-tools/for-organizers.md
Normal file
|
|
@ -0,0 +1,68 @@
|
|||
### Infrastructure
|
||||
#### Google Drive
|
||||
We used the following Google Forms/Spreadsheets/Docs. Create your own versions of them and then update the links in your own documentation
|
||||
* Data Tracking Form (Google Form)
|
||||
* Fields:
|
||||
* What is the title or general topic for this file
|
||||
* URL webpage
|
||||
* Suggested Action (Describe, Capture, Review, Translate, Other)
|
||||
* Rationale - Provide a brief statement on value. Based on your experience, why is this important to preserve?
|
||||
* Do you need to upload files/datasets? (yes, no, maybe) - also has a link to Work Completion Form with a note that you can upload files
|
||||
* Other notes, comments - if you have data to transfer to us, please leave your email or check in with us for a separate upload link
|
||||
* Linked from:
|
||||
* [Track 2](../how-to-start/track-2-data-assessment.md)
|
||||
* [Track 3](../how-to-start/track-3-technical.md)
|
||||
* Data Tracking List (spreadsheet result of Data Tracking Form)
|
||||
* This is for adding metadata to the data submitted to the Data Tracking Form. You can either link people to the form results, or copy things over to a different sheet that people can add to
|
||||
* Linked from:
|
||||
* [Track 2](../how-to-start/track-2-data-assessment.md)
|
||||
* [Track 3](../how-to-start/track-3-technical.md)
|
||||
* Work Completion Form (Google Form)
|
||||
* Fields:
|
||||
* First Name
|
||||
* Task - Describe what you did in 1-2 sentences
|
||||
* Completion Status (Completed, Needs further review, Incomplete, Other)
|
||||
* Notes/Comments - What do we need to know to make sure everything is wrapped up and accounted for? Any further questions/comments.
|
||||
* Linked from:
|
||||
* [Track 1](../how-to-start/track-1-communications.md)
|
||||
* [Track 3](../how-to-start/track-3-technical.md)
|
||||
* (Optional) Digital Research Repository outreach template ([See example from Seattle Data Rescue](https://docs.google.com/document/d/1OjEUMV00Kn1axqIBUlt44tFYCOSKDhIQXZzG8J3xIas/edit?usp=sharing). Linked from [Track 1](../how-to-start/track-1-communications.md).
|
||||
* Research Team Summaries (Google Doc)
|
||||
* Editable doc with prompt - see [Seattle Example](https://docs.google.com/document/d/1BH24Ks63J55K1jFmdUxUKubuqusCAxwU-9verrfjTbc/edit?tab=t.0#heading=h.7otnd3urnwqn). Linked from [Track 1](../how-to-start/track-1-communications.md).
|
||||
|
||||
#### Short-term repositories
|
||||
* For the Seattle Data Rescue, we used several different options to transfer data—participants could submit small files via a Google Form, they could use WeTransfer, or they could email it to the organizers. Use whatever resources you have (including these and others), but be aware that all may have size and institutional affiliation limitations.
|
||||
* These repositories should be linked on the [Track 3](../how-to-start/track-3-technical.md) documentation
|
||||
|
||||
### Customizing this Gitbook
|
||||
You're welcome to fork this Gitbook or reuse the contents in other forms as desired. Several pages, including [Collecting Scope](collecting-scope.md) and [Community Agreements](community-agreements.md) include information that is not relevant outside of the Seattle Data Rescue events, but is included to help organizers develop their own information.
|
||||
|
||||
Don't forget to update the Community Scope and Community Agreement, remove the info tags at the top of some of the pages, and add in links to your own infrastructure.
|
||||
|
||||
### Suggested Frequently Asked Questions for communications
|
||||
|
||||
Q: I am not feeling well, will you provide basic PPE (masks/sanitizing wipes)?
|
||||
|
||||
A: This is a mask-friendly event, and we encourage attendees to bring and wear masks for added protection against COVID-19. We encourage everyone who might feel under the weather to either attend via zoom OR come to the next Data Rescue event (if condition improves).
|
||||
|
||||
#### Q: What devices or equipment do I need to bring?
|
||||
|
||||
A: This is a BYOD (Bring Your Own Device) sort of event meaning participants are invited to bring along whatever devices they might need to contribute their skills. If this means just a pen and paper, that’ll do! NOTE: we do have a limited supply of laptops in case yours goes on the fritz last minute.
|
||||
|
||||
#### Q: How much programming or technical skills does a participant need?
|
||||
|
||||
A: For these Data Rescues, we only require surface level understanding of technology meaning do you know key differences between a physical and digital, do you have basic computer skills or have an interest in developing more, and can you understand the core threats to digital files like deletion and corruption?
|
||||
|
||||
#### Q: Is there anything I need to read or review in preparation for the event?
|
||||
|
||||
A: There is no required reading prior to attending the event, but you are welcomed to explore our [Gitbook documentation](https://calma.gitbook.io/datarescue) that shows suggested tasks, some potential readings, and overall information on the event structure.
|
||||
|
||||
#### Q: Do I need to be there the entire time?
|
||||
|
||||
A: No, these Data Rescue events are set up as Drop-Ins where most people can complete a digital preservation task within the hour. No one is expected to stay beyond that or arrive right at the start of the event. 
|
||||
|
||||
#### Q: Can I bring a friend?
|
||||
|
||||
A: Yes, friends and family (all ages) are welcome but please note that we are limited in in-person space. If more people arrive than we anticipated, we may ask you and your guest to move to our overflow spaces (both online or in-person). You are also welcomed to invite your friend to attend the next Data Rescue event.
|
||||
|
||||
Contact [example@mail.com](mailto:example@mail.com) for questions and/or more information. 
|
||||
|
|
@ -6,6 +6,10 @@ description: >-
|
|||
|
||||
# Readings
|
||||
|
||||
{% hint style="info" %}
|
||||
You can also check out the [Updates](updates.md) page for more updated news regarding federal websites and data.
|
||||
{% endhint %}
|
||||
|
||||
ClimateWire, S. W. (n.d.). Climate Web Pages Erased and Obscured under Trump. Scientific American. Retrieved January 3, 2025, from[ https://www.scientificamerican.com/article/climate-web-pages-erased-and-obscured-under-trump/](https://www.scientificamerican.com/article/climate-web-pages-erased-and-obscured-under-trump/)
|
||||
|
||||
Dillon, L., Walker, D., Shapiro, N., Underhill, V., Martenyi, M., Wylie, S., Lave, R., Murphy, M., Brown, P., & Environmental Data and Governance Initiative. (2017). Environmental Data Justice and the Trump Administration: Reflections from the Environmental Data and Governance Initiative. Environmental Justice, 10(6), 186–192.[ https://doi.org/10.1089/env.2017.0020](https://doi.org/10.1089/env.2017.0020)
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ Other suggested alternatives include:\
|
|||
|
||||
In a surprise move to no one, thousands of federal files, websites, and datasets were either removed, scrubbed, revised, or simply put offline. Crucial areas of research, teaching, and community knowing including life saving Public Health issues for marginalized populations in particular are experiencing ruthless obstruction of online information sharing. \
|
||||
\
|
||||
This year's extensive purging of government data is also a reaction by federal agencies to the disastrous January 2025 Executive Order to freeze government research funding until agencies can confirm that their work aligns with the new government's ideologies. For [UW updates ](https://www.washington.edu/provost/federal-policy-updates/)see Office of the Provost website
|
||||
This year's extensive purging of government data is also a reaction by federal agencies to the disastrous January 2025 Executive Order to freeze government research funding until agencies can confirm that their work aligns with the new government's ideologies.
|
||||
|
||||
As many scramble to gain or give access to tampered websites and datasets, the following news articles are just a starting point.
|
||||
|
||||
|
|
|
|||
|
|
@ -16,8 +16,7 @@ Through multiple hour-long sessions held at universities, public libraries, and
|
|||
|
||||
Given these frightening scenarios and risk factors, the Seattle community can work together to triage a potentially disastrous scenario for the United States, the public, and our publicly funded government data. Others like the [Environmental Data and Governance Initiative](https://envirodatagov.org/) (EDGI), [Silencing Science Tracker](https://climate.law.columbia.edu/Silencing-Science-Tracker), DataLumos, and the [End-of-Term Project](https://eotarchive.org/) are continuing the work from 2016 with ongoing monitoring, collecting, describing, and preserving at-risk data. Even more recently state lawmakers from Massachusetts, Hawai’i and North Carolina have introduced legislation the [“Public Archives Resiliency Act](https://www.markey.senate.gov/news/press-releases/sens-markey-hirono-and-rep-adams-introduce-legislation-to-promote-conservation-and-preservation-of-government-and-historic-records)” to safeguard vulnerable government data. 
|
||||
|
||||
In an attempt to also respond to the potential loss of vital information about our environments, the University of Washington Center for Advances in Libraries, Museums, and Archives ([CALMA](https://calma.ischool.uw.edu/)) in collaboration with local Seattle cultural heritage consultants, BKS Studio, will host two Data Rescue data preserving events in January. Data Rescues will be held on Wednesday, January 15, from 12:30 to 5:30 pm and Wednesday, January 22, from 12:30 to 5:30 pm at the University of Washington Seattle campus in the [Suzzallo Library](https://lib.uw.edu/suzzallo/) Open Scholarship Commons. All skills, ages, and backgrounds welcomed with Data Rescue coordinators available to assist volunteers with tasks, technology, and questions. Additional information can be found on the [CALMA blog](https://calma.ischool.uw.edu/data-rescue-events-to-preserve-at-risk-government-data/). 
|
||||
|
||||
Data Rescue volunteers will participate in the process of preserving online public government data, understanding which types of data are most at risk, and begin the actions of rapid response data preservation. Local efforts aim to bring attention to both ongoing and upcoming threats to vital information that will be necessary for continued efforts at restoring and repairing environmental damages and social tension, the work cannot end there. Even after the inauguration and DataRescue events, Data Rescue coordinators will facilitate skill building and commitment to data preservation while opening up dialogue with others in the Seattle and Washington community on how our city and state can advocate for data integrity and environmental protection.
|
||||
|
||||
For more information or information on how to cover one of the Data Rescue events, please contact [calma@uw.edu](mailto:calma@uw.edu).
|
||||
UPDATE: We've added an [Updates](resources-and-tools/updates.md) page with more information on the state of federal data through the first months of 2025.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue