Versions Compared

Key

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

Discussion items

TimeItemNotesAction Items
<5 minsIntroductions
  •  


30 minsERM Sprint 60 Retrospective
  • Key takeawaySprint cycle is practically curtailed, but creates opportunity for 'between sprint' time
  • Improvements to ERM (rather than FOLIO) onboarding


20 minsSprint 61 Engineering Design Notes

5+ minsAOB
  • Add items hereNone

Engineering Design Notes / Queries

Feature

Issue

Summary

Notes

Notes


Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-79

Set supplementary information for a licenseERM-49Set up ERM permissions modelERM-132Manage annotations for license termsERM-92Require UUIDs that are RFC 4122 compliantERM-139Refactor for SearchAndSortQueryERM-173 / ERM-174Manage tags on agreementsERM-162 / ERM-163Manage internal contacts on licenses

  • Some final integration tests to commit
  • Sort order to be implemented

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-49

Progressing dialogue with Wayne to determine implementation options.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-92

Questions around approach to creating domain objects outside of web app context for integration testing, which Kurt will raise on the ticket.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-139

TBD whether to share data or fetch each time. FOLIO preference is emerging to be fetch each time (as eHoldings does). This should be resolved in the UX call on Thursday

This approach will result in more fetches, but this should be mitigated through caching.

No caching has yet been implemented, but this is something we need to plan for and schedule into upcoming sprint work.

Note: deferring the refactor until the routing question is resolved need not delay work on Amendments, but if that is progressed using SearchAndSort (rather than SearchAndSortQuery), it will need re-work later. Decision is to expedite the routing best practice question through UX team, complete the refactor and use the next couple of weeks to get a sense of the impact of additional fetches that caching needs to mitigate.


Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-173
/
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-174

smart-components has been amended to make Tags handling more flexible, which allows for the option to create a new withTags component in stripes-erm-components.

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-162
/
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-163