NUKnightLab / NUKnightLab/StoryMapJS

Respond to Google Drive removing web hosting

Open
#301 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Documentation Examples
Dominant language
JavaScript
Stars
248
Forks
61
Avg merge
1m
Merged PRs (30d)
1

Description

A twitter user observed that some of our examples on the StoryMap home page have broken.

My quick triage is that this is because they were created when StoryMap used Google Drive as its storage. To address this issue we should:

  • test all Knight Lab StoryMap examples, linked from the home page and from possibly the gigapixel page
  • Most of them should have been imported to the S3-hosted version of StoryMap. If so, we can just get a new "share" URL and update the examples links. I believe those are owned by the Knight Lab Google account.
  • If they weren't imported, we may be able to reconstruct them. I can advise further.

Everyone doing tech support should get a basic understanding of what's going on here. I don't think we'll have a ton of questions, because anyone who has logged in to StoryMap since about 0421ce66b2fab7efe9bd0461ba2ff61b9209aab5 should have their work on S3. But we've been surprised before, there are still timelines out there using verite.co URLs

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by testing every Knight Lab StoryMap example linked from the home page and possibly the gigapixel page. Check whether each example was imported to the S3-hosted version, then obtain replacement share URLs or identify examples needing reconstruction. Done means the listed examples work and their links no longer depend on removed Google Drive hosting.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, content, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.