emory-libraries / blacklight-launch Goto Github PK

Add a CI to ServiceNow for Blacklight. This will be needed for operational support.

Use this form to request the CI

https://emory.service-now.com/sp?id=sc_cat_item&sys_id=bc1433751333b6000ec059722244b0ef&sysparm_category=4e6cf5f8414eb00079479fbad28ca8df

Create a matrix of where different types of documentation are stored, for the purposes of this project phase.

• DLP sample: DLP Wiki version
• Template for what's on the Wiki pages Google doc

• Create an elevator speech from general communications talking points that can be shared with Emory Libraries Leadership team so they can help communicate and promote the Catalog.
• Present to Rosalyn for approval

As indicated on the revised roadmap, demonstrations will be recorded during each sprint to introduce libraries employees to specific features in Blacklight.

• The demonstration will show the work completed and how the feature works in Blacklight.

• The demonstration will show the differences between Blacklight and discoverE where the feature is concerned.

• Users will be warned about possible discrepancies with testing that data may not be immediately current depending on development work in place.

• Demonstration to be recorded by Lovins on 7/30/21 and sent to SEND Team for review

• SEND Team will review prior to 8/3/21 and bring any questions or concerns to SEND team meeting on 8/3/21 for discussion.

• Any edits to demo will be made by Lovins by 8/6/21 for distribution with status report, and send demo with email update will be sent to LibAll listserv on 8/9/21.

See Support Document for output for this ticket.

We need team agreement on the definitions of Alerts so we have the same expectations about how those alerts are managed.

The team has a current deadline of Friday June 18th to contribute edits to the definitions for:

• Hard Alert (paging/major incident)
• Hard Alert (bug/problem)
• Soft Alert: (health related and should be monitored for a planned response )

Links to deliverables folder

Deliverable Acknowledgement Form - General Items

This epic includes tasks related specifically to project closeout and documentation.

See Support Document for output for this ticket.
The team needs to agree on definitions for AWS related alerts so we all have the same expectations about how those alerts are used and managed.

The team has a deadline of Friday June 18th to contribute edits to:

Soft alerts

• CPU
• DISK
• MEMORY
• OTHER

Hard alerts

• solr process not responding
• apache not responding

See Support Document for output for this ticket.

• Identify the purpose of each alert and determine / validate thresholds reflect an operational metric (I.e. some may be going off after a single failure so we may want to adjust that to multiple failures over time)
• Decrease in-actionable alerts from AWS to improve the usefulness of the alerts we are getting.
• See if we can improve the wording of the alerts.

Internal and external communications planning and execution

In order to properly plan for the possible sunsetting of discoverE, a diagram has been created to illustrate the interdependencies of discoverE that must be addressed before the application can be sunsetted.

A meeting has been scheduled to meet with various stakeholders who have direct insight into discoverE interdependencies.

In order to start delivering communications to stakeholders regarding changes coming to Blacklight Discovery Layer, an initial meeting is needed with a member of the CCR team who can help determine the completeness of the plan and where CCR might be able to lend assistance.

• Need to identify people who have knowledge, skills, and abilities for completing certain tasks in AWX when alerts are received.
• Who is on point when an alert comes in (primary, secondary, informational)

• What test plans are needed for beta launch?

• Change freeze for Beta Launch

• Determine dates

• Determine scope of freeze

• Determine types of features/functions that will freeze

• Determine dependencies of features/functions that need to be in place before freeze

In an effort to have a meaningful conversation with members of Senior Management Team, the change in timeline and scope must first be approved by Executive Sponsor. An updated roadmap has been presented for her review along with a proposed presentation to be shared with members of SMT.

Change Management Toolkit

In order to provide stakeholders with how refinements will be handled post production launch, I would like to discuss how we might plan for refinements at the portfolio level for all products managed by LTDS.

Infrastructure handoff/knowledge transfer from DCE. This mitigates a project risk that if the middle-ware positions aren’t filled before the end of the project, then application support will be limited, and a significant amount of responsibility will be placed on Ann 

Output: Identify a playbook and workflows for support
Related info:
Support Documentation on the Wiki

Finalize the support process flow diagram (will be used for the OLA)

I would like to go ahead and run an accessibility test and review the report to see if there are any urgent fixes needed. The majority of the fixes will be planned for Phase 2. As part of Phase 1, I would like for the following tasks to be completed

• Run Lighthouse on Home Page
• Run Lighthouse on Advanced Search Page
• Run Lighthouse on one static page (e.g., About)
• Run Lighthouse on search results page
• Run Lighthouse on Single Item View page
• Determine next steps for accessibility remediation

• Review alert slack channel uses

Draft OLA

Setup CI in ServiceNow

TICKET 262: Confirm Thousandeyes is implemented for paging

Review OLA with Scrum Team and Product Owner

LTDS-L Approval of OLA for Beta period

Schedule 30-day review to review OLA for any adjustments prior to production launch

Documentation for Blacklight Support lives in the wiki.
https://wiki.emory.edu/display/BDL/Operations
This ticket is to document the current state of the following monitoring tools, what they are, who has access, and what actions are needed to complete any setup or configuration in this sprint and what actions/tickets are needed in future sprints. Monitoring tool documentation is in the following priority order:

Cloudwatch Documentation: https://wiki.emory.edu/display/BDL/Cloudwatch+Documentation
COMPLETE: actions are for team review the document and add a new ticket for AWS Hard Alert paging in ServiceNow.

Thousandeyes Documentation: https://wiki.emory.edu/display/BDL/Thousandeyes+Monitoring
COMPLETE: actions are for team review of the document and schedule ticket #262 for sprint work right before beta launch

Honeybadger Documentation: https://wiki.emory.edu/display/BDL/Honeybadger+Documentation
IN PROGRESS: Collin will do a first draft then the team will review the document for any other actions if needed

Support Documentation on the Wiki

Finalize the support process flow diagram (will be used for the OLA)

In an effort to break up the work for completing all functional tests and user acceptance tests, the product owner will work with the product manager to finalize the test plans for basic search.

Acceptance criteria:

• Drafts of tests reviewed between PO and PM

• PO will run through the tests to determine if any edits are needed

• If not edits are needed then test plans can be determined to be complete until all can be reviewed with SEND team in September.

PO and PM to work together to develop a high level training plan to be reviewed with members of the SEND Team and subsequent stakeholders to ensure delivery of all possible training materials.

Within scope:

• Existing training documents from discoverE that should be updated

• Training delivered by others within the libraries including instructional librarians

• Timeline for completing and delivering training

Using the PMO template, write up the closing documentation. The final approve is provided by Rosalyn.

We have addressed needs around Google Analytics but I would also like to explore what analytics and reports are available through Primo VE. Please reference any information specific to Primo VE analytics and estimate the amount of effort needed to implement these tools.

Document why the alerts are in place and what is supposed to happen when an alert is sent/received. (e.g. restart Solr)

Information reviewers:

• Alex
• Collin
• Ann

• Once OLA's have been drafted, the information should be shared with the functional working areas including certain members of the SEND Team who are directly involved with operations affecting Library Search such as cataloging, special collections, course reserves, doc delivery, fulfillment, and ILL.
• The idea is to have either the feedback form updated to route to these functional areas in the event an issue needs to be reported or have ServiceNow tickets routed to these groups.
• Expectations of referred reports should be included in the OLA.