Web Systems Release Notes: 2017.43

This button enables the Doctors to be displayed who are associated with an Organization in a given Location. Example is https://www.yalemedicine.org/departments/cancer-center/appointments_and_locations.html

Under certain conditions, a Story Tag attached to a Story in the Story Editor would disappear upon a subsequent save of the Story.

Listings of Doctors and Concept Articles will now be re-randomized once per hour.

Prioritize doctors with a headshot image and an academic or professional suffix first in the randomized list of doctors on the Doctor landing page.

Prioritize custom articles first in list of randomized articles displayed on the Condition landing page (https://www.yalemedicine.org/conditions/), instead of including Staywell articles.

This is a code module that is useful to developers but should be disabled in our Production environment.

This data feed will be used to enable editors to easily find Stories and Concept Articles that are missing their Promo Thumbnail images.

This will allow monthly notifications to be sent to Doctors that include thumbnail images for stories and condition articles.

The unlink function appeared not to be working in the YM publishing tool. It does work, but you have to double click on the link to use the link editor.

Add a filter to the YM Article Reporting Tool to filter by Custom, Staywell, or NCI Concept Articles.

Create a filter on the YM Reporting tool to show content without a promo thumbnail so that Production can make sure all content has thumbnail images.

When filtering for Organizations with no Related Doctors, we need to exclude Organizations with associated Care Teams, since such Organizations have no Related Doctors by design.

Add support to Search for "synonyms". If you search for a phrase with the character "&", it should be treated the same as if you had typed "and" (and vice versa).

This automates the generation of configuration information for the YSM websites in Development, Acceptance, and Production.

Added MSLIS (Master of Science in Library and Information Science) and MSI (Master of Science in Information) as academic options in the Profile System.

This was a timezone-related bug.

This Accessibility fix will present lists of links that appear in the "sidebars" of YM pages in a format more understandable to screen readers.

This Accessibility fix allows Alt text to be displayed for video poster images.

This Accessibility fix will enable Alt text to be displayed for images throughout the YM site.

New vanity domains entered in the tool are not rewriting the medicine.yale.edu URL to the custom domain.

Some images are broken when viewing websites via vanity domains.

A large number of databases used for SDL share the same name in our development and production environments. This task is to rename these objects so their role is very clear.

To cut costs, we are eliminating Gliffy from Confluence so we need to export our diagrams to keep copies of them.

This is to change the way the SDL applications communicate with the database server. In the event that the USA SQL Database goes down, our software will automatically connect to the European version causing only a brief outage during the transition.

Gliffy is a diagramming solution bundled in with Confluence but is expensive compared to competing the competing product Lucid Chart which we have started to use. So the question is simply, what becomes of our existing Gliffy diagrams when we stop paying for it? Answer: We should download copies before deactivating.

Our upgrade to the SDL 8.5 environment is complete. This task is to remove virtual servers and databases that are only used by the 8.1 environment.

The live broker database for SDL that serves content for all our sites has an irreparable issue that requires it to be replaced. The primary sites affected are Yale Medicine Magazine and Medicine@Yale. This task is to replace the database in the background so that end users are not impacted during the swap.

As we made progress we realized that this would not resolve the issue and we are currently engaged with SDL Support to diagnose issues with the broker database we attempted to replace.

Azure SQL Database solutions offer two pricing models. This task was to move our SQL databases into the more cost effective solution after evaluating the size and transaction needs of each database.