Notify users about changes to map services

[mitchellryant]

Next week the migration of the ArcGIS Services and WMS services should be complete and DataHub fully updated. I thinking we will need to sort of "banner" on the Collection Card (where wms link is not null). Simply stating services have been migrated to the a new URL and old URL will be active till Jan 1, 2021. They should update there links.

Since this links do not appear on tnris.org, i do not believe anything need to go there.

JH edit: plans to address this issue below --> https://github.com/TNRIS/dataHub/issues/287#issuecomment-724742484

[jwhaney]

I think I understand what you're saying here @mitchellryant, but let me play devil's advocate. If the user has the service url link they want, what is their reason to go back to that collection on the datahub? In other words, how will a banner on that collection telling them that the service url is changing help them if they don't have a reason to visit that datahub collection? And when they do visit the datahub collection again after their service url breaks, then they are already there and they can grab the updated url. Just my thoughts anyway, and my thoughts do not always make sense...

I'm thinking this might be a better email blast or tweet maybe? Idk. I don't have the answer necessarily.

[adambreznicky]

banner is a good idea for those that do visit. i like the tweet and email blast ideas also. we should do all of them! maybe could be a blanket banner opposed to only being present on collection cards with a wms link? could work on tnris.org also

should we also attempt to update the old domain routing in Rte53 to just CNAME, or forward traffic to the new domain so that the old ones don't break?

[jwhaney]

should we also attempt to update the old domain routing in Rte53 to just CNAME, or forward traffic to the new domain so that the old ones don't break?

i like this idea. when in doubt, automate the fix!

[mitchellryant]

@jwhaney You could do an email blast or twitter, but that would mean i would have to talk to them. and talk about what was done. not really my thing. they would probably make a big deal out of nothing. I can publish the last service and turn the EC2 off. I was just hoping to afford question from staff and customers. Given the lack of problem solving skills SM will not check to see if the URLs actually.

@adambreznicky i do not think changing route 53 will work. the old site uses a load balance and wildcart cert. the new route 53 hooks directly to the server and uses a cert load into IIS on the EC2.

the services links are slightly different. band combination is one instead of two.

https://webservices.tnris.org/arcgis/services/StratMap/StratMap14_NC_CIR_6in_Smith/ImageServer/WMSServer

vs

https://imagery.tnris.org/server/services/StratMap/StratMap14_NCCIR_6in_Smith/ImageServer/WMSServer

[mitchellryant]

The use of the email blast or Twitter implied the people using the links are in both of those spheres.

[jwhaney]

talked to FR yesterday about this. the plan is to do all three:

1. modal popup notification across entire data.tnris.org domain so any url visited, the notification will show explaining the migration of services, timeline, and how to remedy (general instructions, like visit the dataset/collection and copy the new service url, etc)
2. email blast using mailchimp (@Ldsmiths might be involved with helping on this)
3. tweet link couple sentences with a link to the mailchimp email page

---

Text for DataHub notification:

In an effort to better organize and enhance the efficiency of TNRIS mapping services, the https://webservices.tnris.org/ domain has been split into two new service domains. There are now separate URLs for vector data map services (https://feature.tnris.org/) and raster/imagery data map services (https://imagery.tnris.org/). All DataHub collections that have a service have been updated with the correct URLs for ArcGIS Server and OGC WMS services. Please update your service connections at your earliest convenience.

All map services utilizing the https://webservices.tnris.org/ domain will no longer be available beginning January 5, 2021. TNRIS strongly encourages users to switch their service connections to the new URLs as soon as possible to avoid an unexpected service outage after January 5th. Please follow the steps below to get updated service information.

1. Visit https://data.tnris.org/ and use the Filter --> By Availability --> WMS Service in the tool drawer to display only collections that have a service available. Use the Search and any of the other available filters in combination with the WMS Service Filter to find the dataset quicker.
2. Within the collection/dataset view, scroll down and on the left hand side, you will see the Online Mapping Service section.
3. Copy the new WMS service url, or the new ArcGIS Services directory URL, to use in your software.

[mitchellryant]

i think it looks good, i would use the full path to the services directory https://feature.tnris.org/arcgis/rest/ and https://imagery.tnris.org/server/rest/. the other link will return an IIS error.

This is what we said last time. 2017

Notice: Effective August 31, all online map services will migrate to a different cloud provider. Old URLs will not work anymore. The most current URLs are on this page. Read more here: Major Changes and Improvements to TNRIS Online Map Services

Major Changes and Improvements to TNRIS Online Map Services
by IS TEAM | August 25, 2017
Effective August 31, all online map services will migrate to a different cloud provider.

What this change means to you:

- The URL for all raster and vector services will change.
- Web services URLs will be consolidated.
- Web services will continue to be hosted as both ArcGIS and WMS services.
- Fewer Orthoimagery web mapping services will be available, however they will continue to be available through our Data Search & Download.
- All NAIP, TOP, and StratMap image datasets will continue to be offered as web map services.

The benefits to you:

> Increase in speed and image quality.
> Increase in number of vector services published.

Also, we’re investigating the potential to publish elevation data services. Stay tuned for this update!

[mitchellryant]

the internet wayback machine is really slow.

[jwhaney]

i think it looks good, i would use the full path to the services directory https://feature.tnris.org/arcgis/rest/ and https://imagery.tnris.org/server/rest/. the other link will return an IIS error.

ya, github automatically makes those domains a link but the intent was not to make them links in the notification. i fixed it in my comment. if we include the services directory you mentioned in the comment above, that's only for arcgis connections? what about wms?

[adambreznicky]

only thing i'd add is a note of suggestion: "TNRIS strongly encourages users to switch to update their service connections to the new domain as soon as possible to avoid an unexpected service outage after January 5th" something along those lines, obviously doesn't need to be those words exactly. i ain't the best linguist

[adambreznicky]

since the survey is getting turned off in data.tnris.org, that popup modal could be used for this notification opposed to a new, separate banner component. @ctrepka designed that modal in an agnostic way to serve this type of situation precisely

[jwhaney]

only thing i'd add is a note of suggestion: "TNRIS strongly encourages users to switch to update their service connections to the new domain as soon as possible to avoid an unexpected service outage after January 5th" something along those lines, obviously doesn't need to be those words exactly. i ain't the best linguist

updated - https://github.com/TNRIS/dataHub/issues/287#issuecomment-724742484

[mitchellryant]

everything looks good to me.

[mitchellryant]

we can not solve this here but once the old server goes away we will have to remind Staff that this happened. The questions will go directly to Imagery POC, I believe that they all go to RDC. They will not remember any of the Twitter, blast, or modal.

[jwhaney]

related to the datahub survey and adam's comment about taking it down in time to address the user notification issue here with the same survey template in the api, is that actually doable? seems to me we would need to change some things or build a separate more simplified version for text notifications. for example, the current template has required fields for the form in the Preview Modal section that do not apply to a more simplified notification to users. also, do we manage the simple notification text in SurveyJS? because there is no option to enter simple text in the api form. i may be missing something, but seems for this particular purpose we may need a new simple modal notification setup, but i'm totally open to ideas.

@ctrepka, @JasonKleinert, @adambreznicky please let me know yalls thoughts on this when you have time. thanks.

[ctrepka]

@jwhaney Yeah, the way it's currently set up, the apiModal might not work for a simple, single window alert. However, with some minor adjustments to the front-end logic, we could probably make it work well for our needs. For example, we might set it so that if there is not a survey in the full modal, and there is not text or a header for the full modal, the preview modal is the only popup to appear and goes directly to closed state instead of minimized when exited. We could talk about this more in detail (particularly about where the alert content would be managed, in the api or surveyJS), but I think a minor reworking of the current modal solution would make this possible so we don't have to make an entirely separate component.

[JasonKleinert]

Just throwing this out there. We used to have a beta notice when we first launched the site. That code is still in the catalog component. We could easily reuse this if a modal is what y'all want. This modal comes up every time the page is loaded, it does not have any connection to local storage. It may be more appropriate to have a banner at the top of the page for the note about the service urls, but that is up to you. Here's what that modal looks like: