Facilitate getting a digital object identifier (DOIs) for StoryMaps. To boost usability of story maps in academic circles, it would be helpful if Esri had a process for DOI generation. The current process is complicated.
I like the idea of there being a digital object identifiers for StoryMaps. But when you mint a DOI you are promising the permanence of the resource -- that as much as possible it will always resolve to the object in question. For example, we mint DOIs at the library data repository where I work. We may migrate to a new system soon, but if we do we will fix what link is registered under the DOI so that it points to the migrated datasets. But there isn't the same promise of long-term availability with StoryMaps. In 10 years, when the current version of StoryMaps starts looking outdated, will projects be kept available or automatically transformed into a new format?
I was thinking more along the lines of creating a locked archive version of the StoryMap, leaving the working copy available. It would have to be hosted long term by Esri similar to the old versions of StoryMaps that are still viewable but not editable. Our faculty are using StoryMaps more often now for publishing research and presenting at conferences.
I very much support the idea of there being permanent archived versions of StoryMaps! The old version of story maps is exactly what I am thinking about when I say that DOIs are not currently feasible. The classic story maps templates will be retired in October 2025 (projects will be permanently taken down as the templates stop working and no longer be viewable). There would need to be a system that is more permanent and stable in place than there has been for classic templates.
I like the idea but in my understanding it is difficult to generate DOI for web-apps / maps especially, when technology changes and older versions gets discontinued.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
