/
2018-02-21 Meeting notes

2018-02-21 Meeting notes

Owned by Tim Whitlock (Deactivated)
Last updated: Apr 05, 2018

Date

Attendees

Apologies

Goals

  • Review Outstanding tasks
  • Look at none UKRDC tasks coming up 
  • Set targets for next week

Discussion items

ItemWhoNotes
Outstanding Items

Tim Whitlock (Deactivated)

  • foghorn_leghorn (Unlicensed) has responded to the matching querires from NHSBT and returned a corrected file and is awaiting their response.
  • rapolas (Unlicensed) has a demo of the BCH RaDaR ready however has some issue with the logo files not scaling well for the space. The IT department has come back about the proposed linux spec saying they don't have the experience for running a linux server. Whilst there is the possibility of running RaDaR on windows it hasn't been tested and would require some of the libraries to be changed as they don't all support windows. The whole web proxy configuration would also be different and we would not be able to offer guidance and assistance.
  

rapolas (Unlicensed) is clearing outstanding RaDaR tickets when not focussing on other tasks

foghorn_leghorn (Unlicensed) is trying the branching approach for validation releases as Fran and Shaun have reviewed the changes in the current test build and asked for it to be released.
JIRA/Confluence

A discussion was had about the use of confluence and JIRA. The aim being to use Confluence to specifiy and document developments with a link from the page to the associated tickets. Making the development process...write up the requirements/specification on confluence using a standard template this page would serve as the link to JIRA tickets and other documentation and specifications.

This does mean we need to ensure we correctly fill in the JIRA tickets. Clearly stating the requirements or linking to the specification documentation. When work is done it needs detailing under the work tab. The comment should be exactly that document queries and discussions with respect to the ticket. If this results in a change/fix at odds with the specification in confluence that should be updated to document this with a link to the ticket etc.

The whole aim is to ensure proper documentation is created as part of the development and maintenance process and not after the event when it won't be done and the detail is forgotten. Confluence allows the inclusion of snippets from Bitbucket so in some cases referencing the code may be a quicker/clearer way to explain the changes rather than writing up a description.

The use of specific JIRA projects for each development allowing the use of version references and components rather than a generic bucket for all developments is also planned.

All these proposals will be subject to review since they need to help manage and control the development cycle not hinder it.

UKRDC string trimmingrapolas (Unlicensed)

An issue on the UKRDC matching where some names had an extra space after the text caused the EMPI to mark the item as needing reviewing rather than matching. All other elements matched. This was raised with nick who came back with:

The repository itself (UKRDC3 database) does not adjust data so will just store what’s provided. The EMPI (JTRACE) arguably could/should adjust data but we’ve never had that conversation… Easy to do, but some clarification required:
a. Which fields?

  • I assume given name/surname/gender

b. Other changes?

  • i. What about capitalization? Presume we should store all in upper case
  • ii. What about standardization for Gender – or are we happy that they do conform to a standard vocab coming in?

A discussion was had about this and it was felt the EMPI should trim the names so that surrounding spces don't impact the matching. No descision was made around capitalisation and standardisation for gender.

Action items