Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
TBD
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: R1 2021
-
Component/s: None
-
Template:
-
Epic Link:
-
Development Team:Leipzig
-
Calculated Total Rank:49
-
Rank: Chicago (MVP Sum 2020):R4
-
Rank: Cornell (Full Sum 2021):R4
-
Rank: Duke (Full Sum 2021):R1
-
Rank: 5Colleges (Full Jul 2021):R4
-
Rank: GBV (MVP Sum 2020):R1
-
Rank: Grand Valley (Full Sum 2021):R4
-
Rank: hbz (TBD):R4
-
Rank: Leipzig (Full TBD):R1
-
Rank: Mainz (Full TBD):R1
-
Rank: MO State (MVP June 2020):R3
-
Rank: TAMU (MVP Jan 2021):R4
Description
Depending on a setting,
A library staff person entering a new patron record wants the system expiration date to be automatically populated based on the patron group. A table in settings is referenced for the expiration dates.
or
the staff person wants the dates to be defaulted to a simple date set in settings,, i.e., +2 years, which can be overwritten when creating the new record if necessary.
Feedback from SIG discussion from 3 Feb 2021:
IF the exp date is in the past THEN calculation from today, IF exp date is in the future or today THEN calculation from given exp date
TestRail: Results
Attachments
Issue Links
- is defined by
-
UIU-1907
Populate expiration date based on pre-defined offset for patron group
-
- Closed
-
-
UIU-1908
Pre-define expiration date offset for patron group in settings
-
- Closed
-
-
UIU-1951
Validate value for expiration date offset (settings) in frontend
-
- Closed
-
-
UIU-2046
Calculate new exp. date not only from today
-
- Closed
-
-
UIU-2058
Rewording for text on expiration date modal
-
- Closed
-
