Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PC update

Minutes

A small group of members of this SIG spoke at PC to talk about issues of data integrity issue causing delays of implementations, problems for those that have implement. The request was for an increase of focus on data integrity.

Philip commented that the conversation was interesting to hear it framed as a data integrity issue rather than strictly a data import issue. Philip mentioned Mike Gorrell's idea the reviewing the flow of data is important.

Documentation Working Group gave an update

Tod Olsen - testing - who is responsible for testing "end to end" workflows.

Khalilah Gambrell gave an update. Kristin brought up the issue of working on new issues vs. working on issues of data integrity. There was a conflict in the discussion as to whether work on new issues would be done or the focus would be on securing the foundation of FOLIO for integrity purposes.

Christie noted that we may be seeing now the limits of the UI driven method of development and documentation. 

Brian asked what exactly the data integrity issues are. Laura acknowledged the importance of this question, but was hesitahesitant to 

Charlotte noted that our data is not in sync across apps and this needs to be solved. She described this as a communication problem and technical hurdle.

Laura clarified that there is no criticism meant towards product owners, but rather that they need more support. 

Patty emphasized that it is the subject matter specialists' job to specify functionality.

Christie - a part of the discussion needs to be "how to we address this issue"? SRS evolved organically. Since SRS did not start out with a UI, it was developed without the input of SMEs. Addressing does not mean we have to completely change the process. 

Laura has found it helpful when Charlotte facilitated conversations between SMEs and developers.

Magda - From a PO point of view, there is more interest in application now because libraries are getting ready to live. This functionality was available many releases earlier, but not tested adequately. If SME's made these discoveries earlier it would have been much more helpful, less expensive.

Laura - finding ways as SMEs where we are finding 

Jason - 

Other updates, announcements

Do we need to consider prioritization for:

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1892
which 

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIIN-340
is part of

Mark for deletion

Review

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1363

QuickMARC development updatesKhalilah Gambrell
Productivity stats "alternative" (aka workaround) (if time)Laura E Daniels

Demo of Cornell's planned approach until

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2867
is implemented

(see Alternatives for Features Still in Development)


...