Course Reserves (UXPROD-791)

[UXPROD-634] Set Term and status for a Course Created: 23/May/18  Updated: 17/Mar/22  Resolved: 17/Mar/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2020
Parent: Course Reserves

Type: New Feature Priority: P2
Reporter: Anya Assignee: Kelly Drake
Resolution: Done Votes: 0
Labels: courses, po-mvp, q4-2019-spillover, team-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-1307 Courses:Pending Courses Closed
relates to UXPROD-1308 Courses: Active Closed
relates to UXPROD-1309 Courses: inactive Closed
relates to UXPROD-1310 Courses Control Vocabulary: Terms Closed
relates to UXPROD-1311 Courses Control Vocabulary: Departments Closed
Epic Link: Course Reserves
Front End Estimate: Small < 3 days
Front End Estimator: Mike Taylor
Back End Estimator: Kurt Nordstrom
Development Team: Thor
PO Rank: 80.6
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R2
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: Leipzig (Full TBD): R2
Rank: Leipzig (ERM Aut 2019): R5
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Library staff associate terms, with their start and end dates,to a course for the following reasons:
So that they, and library patrons can know if a course is pending (set to occur in the future), active (occurring now), or inactive (having occurred in the past)
In order to find, run reports and export results for courses that are pending, active, or inactive.
In order to find, run reports and export results for courses by date
In order that items added to a course, by default, can inherit the Course “Start” and “End” date values into the Item “Start” and “End” date fields respectively.

(There is no explicit “state” field (“pending”, “active”, “past”) associated with a term: instead, the current state of a term can be determined when needed based on the current date, and “state” searching can be implemented as a date search based on the current date.)

This section includes a “Select term” box, that is prepopulated with Terms (configured in the Course Reserves Settings) and their associated “Start date” and “End date” fields.

Having selected the correct term in the “Term” box, users can edit the prefigured start and end dates prior to selecting the enter button.

Users with appropriate permissions may change the Term, start and end dates in Settings.
If a user does change the Term, start or end dates after a course is created the term, start and end date of every item associated with the course will update to the new term dates, regardless of whether or not the item start and end dates had been modified from the existing term dates. When changing the Term, start or end dates the user is warned that “Changing the Term, Start or End dates of a Course will change the Term, Start or End date of all associated items.”

The Active status is a checkbox

_-------2018 Course Reserves -----

The scheduling of a course in FOLIO

There needs to be a drop down to assign a controlled vocab ( summer, winter, fall, spring, or Q1, Q2 etc) Term. Those terms like the Fix date loan rule have an assigned lengh of time associated with them that was pre-entered.

Then if the admin needs to change the dates they also have the ability to override the dates

see po created mock up: https://folio-org.atlassian.net/wiki/x/jR8i

The future date should have the status of Pending
The Active falls on and between the course/term start and finish date
The past dates should have the status of Inactive



 Comments   
Comment by Cate Boerema (Inactive) [ 30/Jul/18 ]

Anya it looks like you didn't get a backend estimate on this. Can you please follow up with Jakub Skoczen to get one (per the Dev leads by area doc, he is the backend lead for this project): https://docs.google.com/spreadsheets/d/1SktTRFLXckqszKOcFJZdEFLRcXUEDHS_8RvIp_Jjpxc/edit#gid=0

Comment by Anya [ 30/Jul/18 ]

Jakub Skoczen- would you please provide backend estimates on this - on the other UXProd-622, and UXprod-628 you estimated medium

Comment by Cate Boerema (Inactive) [ 07/Nov/18 ]

Anya, I don't see any stories linked to this feature, but I am pretty sure you said the backlog was complete. Can you please link this up and mark it Analysis Complete? Thanks!

Comment by Anya [ 29/Mar/19 ]

Comment from March Meeting: Hkaplanian and Anya to Make a Plan

Comment by Holly Mistlebauer [ 23/Sep/19 ]

Holly changed the Fix Version from Q3 2020 to Q4 2019. Features with a Label of cap-mvp must be scheduled for Q4 2019 at the latest.

Comment by Mike Taylor [ 25/Sep/19 ]

Part of this estimate is for the relevant front-end CRUD support.

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