Select to view content in your preferred language

Converting or Exporting Crowdsource StoryMaps?

133
3
Jump to solution
a week ago
SaraJL
by
Frequent Contributor

In my adventure in converting StoryMaps for faculty, I've run into these Crowdsource template StoryMaps that I'm a little unsure what to do with. They were created before my position here, so I'm a little unsure on how these were setup.

It looks like there might be credentials attached to them that are separate from our org credentials? We decomissioned our GIS Server, so I'm wondering if that's what it was attached to - although, I know we didn't have any data stored on our server, so that couldn't be the case.

Link to the map

(screenshot - I purposely left out the actual credentials, so hopefully this makes sense)

SaraJL_1-1759244677364.png

Can I just delete the credentials on a Crowdsource StoryMap? I'll admit that I've never used one of these.

Has anyone been able to convert one of these Crowdsource maps to the new template? If this helps, we're not really interested in preserving the ability for people to still add data, only visualize what is currently on it. So if there is a way to pull the data out, I might convert it to a Map Tour or something instead.

0 Kudos
1 Solution

Accepted Solutions
OwenGeo
Esri Notable Contributor

@SaraJL - The data from a crowdsource story is stored as a feature layer. Just find the feature layer item that goes with that story, and you can easily use it to directly create a map tour in ArcGIS StoryMaps.

The OAuth credentials are there because the Crowdsource Story Map had the ability to track who was contributing to the app. There's no need to delete them, but shouldn't be any harm in it either.

When the classic templates are retired, the items related to them will still remain. So there's no danger in using the original feature layer to create a map tour. However, if you want to extract the information into a new feature layer you can do that using the workflow in this blog: Migrate a classic Shortlist to ArcGIS StoryMaps as... - Esri Community.

Owen Evans
Lead Product Engineer | StoryMaps

View solution in original post

0 Kudos
3 Replies
OwenGeo
Esri Notable Contributor

@SaraJL - The data from a crowdsource story is stored as a feature layer. Just find the feature layer item that goes with that story, and you can easily use it to directly create a map tour in ArcGIS StoryMaps.

The OAuth credentials are there because the Crowdsource Story Map had the ability to track who was contributing to the app. There's no need to delete them, but shouldn't be any harm in it either.

When the classic templates are retired, the items related to them will still remain. So there's no danger in using the original feature layer to create a map tour. However, if you want to extract the information into a new feature layer you can do that using the workflow in this blog: Migrate a classic Shortlist to ArcGIS StoryMaps as... - Esri Community.

Owen Evans
Lead Product Engineer | StoryMaps
0 Kudos
SaraJL
by
Frequent Contributor

Thank you @OwenGeo - this is super helpful!

I'll see if I can track down the feature layer. I may leave it up to the faculty member to see what they want to do with it (make a Map Tour or put it in an Instant App can all it a day)

Part of the reason why I want to try and remove the OAuth credentials is for troubleshooting reasons - I'm running into an issue with a few of the Crowdsource StoryMaps where I'm unable to open them in the edit view. If I click on Configure it's stuck in a loading loop, so I'm just trying anything I can think of to get it to open. I haven't checked them all yet so I don't know if it's all of them, but at least 2 of them have the issue.

If it runs off a feature layer, than I might not try too hard to view it in edit mode, but it's definitely curious.

0 Kudos
OwenGeo
Esri Notable Contributor

@SaraJL - The Crowdsource Story Map template was only ever a beta/experimental template and was deprecated in 2018. It hasn't been updated in many years, so I don't believe the builder is likely to work any more.

Owen Evans
Lead Product Engineer | StoryMaps
0 Kudos