Web Systems Release Notes: 2017.42

Accessibility Fix: Correct the media icon overlay on video and slideshow content to display AltText for accessibility screen readers.

The inline link editor for Stories and Condition articles works inconsistently in Firefox and IE.

Accessibility Fix: Display AltText in the MyChart sidebar image.

Display phone numbers for locations on doctor profiles from the category "appointments" OR "information and appointments". This addresses the issue where some doctors did not have phone numbers on locations.

Make the byline date on content displayed on the website match the date applied in the YM Publishing Tool.

If a doctor has no phone numbers, do not display an empty "Contact" box in the side column.

Remove the concept lists from the "In this Article" section of the Stories and Condition Articles. The Content team will use the publishing tool to review data instead of the production version of the article.

Create a filter on the YM Reporting tool to show content without Related Doctors so that the content team can adjust tagging to produce Related Doctors. We will add additional filters to limit selection to custom content in next week's release.

An organization membership feed for the Human Practice referring physician app that gives them the same people for the app who are on the YM website.

Remove the duplicate organization name heading on department Appointments and Locations map page.

Display Concept Articles even if there are no Related Doctors associated with the article.

Instead of displaying doctors in alphabetical order when you first come to the Doctors landing page (https://www.yalemedicine.org/doctors/), show a randomized order. After pushing live, we realized that we should prioritize doctors first, which we'll do by boosting those with custom (SDL) bios in next week's release.

Show condition articles in a randomized order on https://www.yalemedicine.org/conditions/ instead of by alphabetical order. We're currently including Staywell content, but in next week's release will boost custom content to be first.

Edit the backend URL used to display Staywell data on the YM website to reduce future issues with infrastructure changes.

Kyruus updated its Expertise Area names and changed the location of some of the specialities. Specifically, they added the word "Pediatrics" before all of the pediatric sub-specialties and made them top-level specialties.

Make updates to the Task Oriented Service (TOS) – the datalink between the YM Publishing Tool and SDL – to let the content team upload videos to articles and stories without adding a thumbnail image. This enables content editors to add videos and then let production add the image later.

Update the Staywell feed to pull from the new server.

Improved handling of parent site titles that appear in the website topper when they are long. They no longer wrap to a second line.

Fixed a problem that caused banner images to appear squished in some banner templates.

Added an image icon next to links to EPS type downloadable files on the YSM websites.

Added a Word icon next to Microsoft Word Template documents (dot, dotx), just as they already did for doc, docx, and other kinds of Word files.

Improve the layout for displaying condition articles and stories to doctors on their profiles in profile.yale.edu. Using this page (e.g. http://prod.admin.profile.yale.edu/Profiles/59693/YmArticles/Edit) a doctor can view all of the content in which they are tagged on the Yale Medicine website, and if they choose, disassociate themselves from the content.

Users could not upload some files to the flyer and thumbnail fields of events in Safari. This bug has been fixed.

Change the data feed used for the event preview so editors can preview events that haven't been published yet.

The "Edit Event" links that appear in event detail popups on YSM websites now link directly to an individual event occurrence in the Profile System if the event is a recurring event.

Calendar administrators are receiving Suggested Event notification emails on the weekend when they're not working. This limits notification to Monday through Friday.

Currently our SQL databases are stored in a single region in the US which puts our websites at risk should something go wrong in that part of the country (think hurricane or other potential disasters). This story is to create a copy of our data to store in Europe so that should something happen to our data in the US, the European instance will takeover and we will still be up and running.

Task is to move databases into a pooled database server that shares resources and reduces our costs.

Azure makes it easy to delete things like virtual servers, web applications and virtual network interfaces. An accidental deletion could mean many hours of downtime. This task is to install locks so that important resources cannot be deleted without significant effort.

RAM consumption needs an adjustment with some of the backend services running SDL.

This is to distinguish the four environments so we are sure we are not testing things in production.

The NCI application runs daily to fetch the latest data from the PDQ Cancer Database and is the last running application on our old server stack, so moving this will allow us to eliminate two servers that we no longer need.

Increasing server memory to address issues where SDL publishing stops running.

Create a new test environment for the SDL Content Management System to enable better regression testing before pushing updates to the production environments.

The current setup uses the older 8.1 environment combined with the new 8.5 environment. This task is to review and move all integration points off the 8.1 version to the 8.5 version.

Vanity URL Rules are broken into two parts, inbound and outbound, this is to address outbound rules which are not working in the new setup.

This is to secure the connection between the application the tech team uses to edit rules and the application that deploys the rules to the server. If this was not secure, then it would be possible for some malicious person to harm our websites.

Vanity URL Rules are managed by manually editing XML files and then replacing files on a set of servers. Given the size of these files, it is easy to make mistakes. This task is to build a web interface for editing the rules and then creating a system that deploys them to the servers to make the workflow of rule changes much simpler and eventually a task we could assign to someone outside the tech team.

Preparations for releasing a new vanity URL management tool that will help the Web Tech team edit custom domain name rules easily.

This is to configure the servers that run the Vanity URL Manager to publish changes to the rules in an automated manner.