Versions Compared

Version Old Version 5 New Version 6
Changes made by

Dennis Bridges

Dennis Bridges

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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-28992565

Problem(s):

  1. Fiscal year rollover can not be "undone"
  2. Fiscal year rollover errors can be complex and difficult, if even possible to correctUser must navigate to inventory to place a request on newly ordered items. This requires additional permissions and breaking up the acquisitions workflow or risking that items are requested before a hold can be place for the desired user.
  3. Title level requests will automatically pull an item that is created by the orders app.

Use Cases & Requirements:

RequirementStatusUse cases

Allow user to generate a rollover report that will tell the user what errors may occur if rolling over with current dataAutomatically create a request for the on-order material so that it can't be taken by someone else. Prevent Title level request queue from picking up this item.

Status
colourGreen
titleVERIFIED

  • In preparation for rollover the library will run a report to catch any errors that may occur so they can be dealt with before the rollover is officially executed.
Allow user to run a rollover "preview" that will show a user the result of rolling over with existing settings
  • At Duke when a patron requests that we order a title, we would flag it as a rush order and capture the patron ID on the order record. Upon arrival a hold is put on the item so that it can't be loaned to anyone else.
  • The hold action needs to happen immediately at the time of order creation to preserve the "first dibs" priority of the original requestor so that they don't get bumped if a request sneaks in as soon as the item is created.

Allow requests to be created for a general user. Possibly system user or a specified generic user account (Requests require a user ID so we can not allow free text when generating request)

Status
colourGreen
titleVERIFIED

  • In preparation for rollover the library will run a report to catch any errors that may occur on account of the rollover settings that are being used, so they can be adjusted before the current fiscal year ends.
Allow user to run rollover "Test" more than once if desired
Status
colourGreen
titleVerified
  • Library will always test rollover to make sure there are no surprises. Rollover may be tested more than once.
Allow user to easily obtain an export of the current years data during rollover process
  • The library does occasionally place holds at point of order without knowing the specific user id. In some cases the requester information could be in a separate system (Eg. Iliad) and a default user is used to identify that this item should be treaded a certain way in the workflow ultimately having a person update the request information so the item is put aside for the correct user.
  • Library is ordering at vendor site and vendor does not have user ID. Allowing requester to NOT be a "user" account would be valuable.

Status
colourGreen
titleVerified

  • When rolling over the system should provide a copy of the closing years budgets (Current state at end of year). This is used  as a reference to help verify the results of the rollover

Proposed workflow:

MiroAccessLinkhttps://miro.com/app/live-embed/uXjVO0CXLbU=?boardAccessToken=cIHC9R75MKqifQ1H54DUwGkU38ilHSgb&autoplay=trueHeight360BoardTitleAllow User to generate a preview of fiscal year rolloverWidth640

VERIFIED



Proposed workflow:



Functionality Potentially Impacted by Changes:

Functional area

Records

Potential impact

Suggested Regression Testing




Questions:

Question

Status

Conclusion

Comments


Status
colourBlue
titleopen




Work Breakdown Structure:

Features:


UI Stories


MOD Stories

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
maximumIssues20
jqlQuery(issuekey in linkedIssues("UXPROD-3435") AND project in (MODORDERS, MODVEND, EDGOAIPMH, EDGORDERS, MODCRED, MODFISTO, MODFUND, MODGOBI, MODINVOICE, MODINVOSTO, MODOAIPMH, MODORDSTOR, MODREC, MODORGS, MODINV, MODCONF, EDGOAIPMH, mod-organizations-storage, mod-organizations, MODEBSNET))
serverId01505d01-b853-3c2e-90f1-ee9b165564fc