Latest Contributions by RupertEssinger

I tried changing the title in my test copy of your Shortlist and I did notice what you describe at first. After that I was able to make the edit OK. I'm not sure what happened, but it only seemed to occur one.  Rupert ... View more

See also this idea: https://community.esri.com/ideas/15730  ... View more

Great. One more tip. In the title or subtitle of your Shortlist, how about spelling out what DNR is. Up to you, but I think it would make the story more friendly when it first appears so your readers know exactly what your agency is. Rupert ... View more

Yes, sorry about the bug. We normally flag a missing image and it definitely shouldn't be preventing issue checking. We've logged that issue to get it fixed. Meanwhile, you could create a blank placeholder graphic, or with the text 'great image coming soon' and use that in your Shortlist to avoid the checking issue.  Good luck with the project too. Your Shortlist looks really nice and we'd like to add it into the Story Maps Gallery if you approve and once it goes live, because it is a neat state-wide example. One tip: in the item details page for your story: https://www.arcgis.com/home/item.html?id=98a7fe4ea3764440ad59f0d9b0b280e3   the brief summary talks about the user. You could change that to 'you' to make it more compelling. Don't forget that if someone shares your story on social media like Twitter, the title, thumbnail and brief summary all automatically appear in the 'social card' that is created. Rupert ... View more

Sorry about how this particular Shortlist doesn't seem to stop checking your story content. We investigated this and there's a bit of a teeny bug in our code in this sort of Shortlist when a place in your dataset doesn't have a picture defined for it.  Check out Manastash Ridge in your "Trailhead use: non-motorized" tab, which is missing its picture. I made a copy of your Shortlist and made a test 'as-is' Shortlist from it. If I delete that place (or supply a picture for it in the dataset) then the checking works OK. So if you fix Manastash Ridge you won't see that issue anymore. We'll also look into fixing that one our end so thanks for raising this with us. Rupert ... View more

It is a good point. We didn't do field mapping because it gets quite complicated. For the enterprise workflow you describe, we'd recommend exporting the data and publishing it with the required fields, and perhaps using field concatenation to add HTML formatting or combine fields together to get exactly the look you want. You could then automate that workflow using scripting in ArcGIS Desktop or ArcGIS Pro to automatically generate the updated data for the Shortlist whenever you want from the source data. Rupert ... View more

Good points thanks. See this FAQ for how to use existing data in a Shortlist: Esri Story Maps - FAQ  Rupert ... View more

Hi Elizabeth, This is a good idea. But to avoid having to make a form/panel editor that could become quite complicated, we took the approach of just accepting whatever the author assembles. Here's how you can do this now. It requires a bit of HTML tagging: - Create an Excel spreadsheet containing all the underlying fields you want to use. Base it on the Shortlist data schema you can download from here: Esri Story Maps - FAQ . For example if you want every place in your Shortlist to have some italic text with the photographers name, add a field in which you store the photographer's name. Use the Excel CONCATENATE formula to define the Description fields (i.e. DESC1, DESC2) by combining the underlying fields with HTML tags in quotes. So the CONCATENATE string for the DESC1 field would include the HTML tags for making something italic and the name of the field that has the photographers' names. - Save the Excel spreadsheet as a CSV file and add that file into a web map. - Share that web map as a Shortlist. When the Shortlist Builder prompts you, choose the 'As-is' workflow. In this workflow, the Shortlist content is driven from a layer in a web map and reflects any updates you make to that web map.Esri Story Maps - FAQ . Save your Shortlist. In as 'as-is' Shortlist you can define a few things in the Shortlist Builder, like the header color, but you can't edit the places at all: instead you manage your places via the web map. So it is all automatic instead of requiring manual updates. - Your Shortlist is now driven from the data in the layer in your map. If you want to make any updates, you can edit your Excel spreadsheet (say to add new records or tabs). and then save it as a CSV file again and upload it again into that same web map, deleting the existing layer too. Your Shortlist will now reflect your updated data. Here's an example Excel spreadsheet set up like this: https://downloads.esri.com/blogs/places/shortlist/Great_Places_ShortlistV2.xlsx  It contains the data I use in this Shortlist: Great Places of America which is a collaboration do with the American Planning Association. This has some HTML formatting for each place that, like you say above, I definitely don't want to have to manually add in via the Shortlist Builder. This is an 'as-is' Shortlist driven by this web map, https://story.maps.arcgis.com/home/webmap/viewer.html?webmap=582069b77fe44ffeb58f26284ca53bd4  which simply contains a CSV upload of that spreadsheet. If you look at the popups in that web map you can see the HTML formatting in the attributes that I defined in the spreadsheet. I do the upload again every year when the APA announces the new awardees.  In that spreadsheet I've color coded the fields so you can see what is going on. White fields and light green fields are used by Shortlist and simply contain the data.  Light blue fields contain data referenced by the formulas in the dark blue fields. So the name of the photographer is a light blue field. After saving out the spreadsheet as a CSV file, the light blue fields can be deleted from the CSV file because they are no longer needed, but there's no need to do that because Shortlist just ignores any fields that are not part of the schema it expects.    Dark blue fields are used by Shortlist and are populated by formulas that combine light blue fields together, with HTML formatting too as required. When you save the spreadsheet as a CSV the returned values of those formulas are automatically written in the CSV file. For example the light blue fields Place_Name, City and State_ab get concatenated into the Name field. My dark blue Desc4 and Desc5 fields are the ones that concatenate several light blue fields together and combine them with the HTML formatting I want. Another nice thing about this approach is that if I change my mind about the formatting in each panel, or the client would like it to be changed or new fields added, I can just modify those formulas in the Excel file once (in the first line, and then use Excel fill-down to update all the records), and then easily update the Shortlist. I definitely don't want to hand edit the layout of the 245 places in this Shortlist. Note that you don't need to use Excel for this workflow. You could also generate the same dataset from inside ArcMap or ArcGIS Pro by using field calculations to do the same concatenation. If you aren't sure how to do that, you could ask them someone on the GIS team who is familiar with that to set up the dataset for you (at least that's what I would do because I've not done field calcs for years ). This workflow does provide some ways to automate the generation of the data to get it into the correct format to drive a Shortlist and make it look the way you want it to look. For example a script could be written to take a GIS layer and publish it for use in a web map with all the fields and HTML formatting set up as required. This would then drive an 'as-is' Shortlist. Note that Shortlist has problems digesting data from ArcGIS Enterprise Server in 'as-is' mode, so I don't recommend trying that. Hope that helps. Rupert ... View more

There are actually three ways to make a Shortlist. - You can start from scratch and add places in the Shortlist Builder. The places you add get automatically stored in a web map that the Shortlist creates for you. You should not edit this web map directly yourself. Only make your edits via the Builder.  OK you could edit that web map to add extra supporting layers into your Shortlist, like a county boundary layer, but that's it, and if you do that, do it carefully. Don't edit the layer that contains the places. And avoid even opening that web map in ArcGIS Online at the same time as you are editing your Shortlist in the Builder.  - You can create a Shortlist from a web map that already contains a point layer containing the places you want to use, and when the Shortlist Builder launches you choose the option to import these places into your Shortlist. Your points don't need to use the Shortlist data schema. The places you import are automatically stored in a new web map that the Shortlist creates for you.You should not edit this web map directly yourself. Only make your edits via the Shortlist Builder. OK you could edit that web map to add extra supporting layers into your Shortlist, like a county boundary layer, but that's it. After you create your Shortlist by importing data from a web map, the original web map you created the Shortlist from is no longer read by the Shortlist, so there's no longer connection between the data in the map you shared and the Shortlist. It's not a live link. - You can create a Shortlist from a web map that already contains a point layer containing the places you want to use, and when the Shortlist Builder launches you choose the option to use these places 'as is'  (aka live link) so the Shortlist will be driven from your original data instead of being imported into the Shortlist and stored in a new web map in its own format. Your points do need to use the Shortlist data schema to use this workflow. With this workflow you can edit the data directly in your web map to update your Shortlist. In fact in this workflow it is the only way to update your Shortlist. With an 'as-is' Shortlist, you'll notice that the Shortlist Builder doesn't even let you edit your places. This is because it is being driven from the web map. Edits you make to the places in the web map, or other changes like adding supporting layers, are reflected in the Shortlist when it is next viewed. For more info, or to see the Shortlist data schema, please see: https://storymaps.arcgis.com/en/faq/#question49  Rupert ... View more

Thanks for the reminder on this. I'm going to log an issue about this. Rupert ... View more