Page Comparison

This page describes the functionality needed for listing course information in FOLIO and will inform Schedule (UXPROD-634)

• • Story | Description

    Library staff associate terms, as well as 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. 
    • Term is used as an identifying field for historical recording
    • May be used for copyright payments for eresources
    
    

    The Schedule 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. 

    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

    • If 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.”

    • and do not fall within the new term dates the system will notify user of the items.

    • OR create a report that lists when item dates fall outside of term dates.  

      Assumptions - Schedule

    • A Course can have only one Term. 
    • Term history is retained for reporting purposes
    • The combination of Term and Course data creates a unique key
    • Term start and end dates are used to determine course status for searching purposes. 
    • Pending (set to occur in the future)
    • Active (occuring nowoccurring now)
    • Inactive (having occured in occurred in the past)
• *Need to think about how to delete courses 
  • Permissions?
    • Should the CRUD permissions for creating Terms be are separate from creating Course Reserves?