[UXPROD-3888] ERM checklists Created: 02/Nov/22  Updated: 30/Nov/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Owen Stephens Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: erm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Release: Not Scheduled
Development Team: Bienenvolk
PO Rank: 0

 Description   

Current situation or problem:

Much work in ERM is cyclical and tends to have a series of well defined steps that need to be carried out each cycle (usually annual). For example when making a decision about renewing an e-resource there maybe a number of key steps that the team need to go through (collection of usage stats, check of license terms, consultation with subject librarians, notify publisher, etc.)

This feature is to introduce a lightweight 'check list' functionality that can be used to help ERM teams with this work.

In scope

Support for check lists on Agreements and/or agreement lines that can be completed each year/cycle

Out of scope

Automation of processes based on data/checklist status

Proposed solution/stories

The initial intention is to build on similar functionality built in the Open Access request management application:

https://folio-org.atlassian.net/browse/UIOA-143

https://folio-org.atlassian.net/browse/UIOA-142

The ERM SIG has previously discussed similar functionality



 Comments   
Comment by Khalilah Gambrell [ 04/Jan/23 ]

Hey Owen Stephens - is it possible for this to be implemented as stripes-component that any app can use? 

cc: John Coburn 

Generated at Fri Feb 09 00:35:36 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.