Web Systems Release Notes: 2017.47

Added summary for NCI articles on search result pages.

Improper HTML tags were saving in some captions, which caused issues for the slide shows.

When there was an error in the SDL Workflow engine, the error messages were not passed to the YM Publishing Tool in a way that the application could notify editors. This task moved these hidden error messages into an interface where we can see/review them.

Suppress inactive organizations from displaying on profiles.

Added the correct iCal feed to the "Add to Personal Calendar" links that appear below each YSM website calendar.

Configure Search Indexing Web Job to deploy and host it within T3 website.

The nightly sync with OnCore (clinical trials) unexpectedly stopped running. It was due to a phone number format change in OnCore.

Fixed bug with input for adding non-Yale locations to events.

Calendar events are not automatically approved when they should be if the event is duplicated and suggested by an administrator or editor of the calendar.

Made event speakers appear in the same order in data feeds as they do in the profile system admin.

Created new feed to pull correct iCal feed for calendars on YSM websites.

Add alternative text for first story image on search result page.

Removed server and all components used to test using a SOLR based index for storing/searching PubMed data for the CV Builder project. This was also used to cost model the use of SOLR for other purposes.

Reduced the size of the objects used in the Development Flyerboard subscription to better match the resource requirements and reduce our costs.

A SQL Elastic Pool is a way to share resources for running database servers in the cloud and is a very cost effective solution.

This task was to reduce the size of the current Program Files drive on the virtual machine from 1TB to 16GB. This change requires all applications to be reinstalled after creating the new, smaller drive. There are three identical servers this will be applied to, this is the second which resides in USA and is only setup as a failover to the primary USA server so there is no impact during this change, even if problems were to arise during the change.

The main production Profile System databases were moved to a subscription to consolidate our SQL databases into one location for both cost savings measures and to simplify Geo-redundancy efforts.

A misconfiguration due to recent server changes was made to eliminate this bug. The NCI download process is working normally again and documentation was updated.

Created some basic troubleshooting documentation for developers to follow in the event SDL stops responding.

We kept the old SDL servers around until we were in production with the new version for at least 3 months just in case we needed to reference configurations from the previous setup. This step created backup copies of all the configurations and then deleted the virtual servers and all associated Azure components.

We have hourly and daily backups of the production SDL database. This moved the storage of the backup files from expensive disk storage to very inexpensive blob storage. In addition, the blob storage was configured to be geo-redundant making it a very safe place to store copies of our data in the event the main SDL server has a critical failure and requires a rebuild.

This task is to consolidate resources for cost savings measures as our footprint has increased in Azure.

Investigation to see if it is possible to reduce the size/cost of a collection of development databases used for the Profile System.

Results: This can be done and as a result was completed as part of a larger database migration.

This task is to change how the production database for YMS is named and also to move it so that it is in the same location as our other production databases.

Results: The current production YMS database will be migrated to a more cost effective solution in our main subscription and also go through a workflow change in how new releases are handled so that the database maintains the same name throughout its lifecycle.

Updated label "Lecture/Presentation" under Activity Map->Add Activity->Activity Type->Lecture/Presentation in profile system to "Speaking Engagements, Presentations, Symposia & Workshops". This will let the faculty better understand where data is stored for the "Invited Speaking Engagements, Presentations, Symposia & Workshops" section in CV.

New Media Library is going to use Azure Media Services (AMS) as a platform to store and deliver video/audio items. This task is about integrating AMS to the project and adding base logic to upload files to the storage and process them.

After media item is uploaded to Azure Media Service (AMS) and processed we need to publish its asset and update info about it in our database. So we use Azure Function app to handle encoding job event from AMS, but Azure Function project is not really standard so this task is about the investigation and incorporation Azure Function project into common deployment process using CI.