Courses - UXPROD-622

This page describes the functionality needed for listing course information in FOLIO and will inform UXPROD-622


Fields:

  • Course data
    • Course Name*
    • Department  (Controlled vocabulary / Authorized value list)
    • Section
    • Course code/Number*
    • Course Type (not mvp)
    • FOLIO ID (unique identifier that is system created)
    • Register ID (interoperability) (Optional)
      • Also used for matching student data (copyright management), especially streaming video
    • External ID (interoperability) (Optional)
      • used for connection to LMS. Need this field name to be generic so that it may be used by other systems and uses. 
      • Could function as link to the page on the external system
      • Option to add additional ID fields with description and link mechanism
    • Cross listed (repeatable field)
      • Unique ID that links to other course.  No parent course? 
      • Linkable field to other Course number
  • Taught by -  allows the user to look up users and allow for more than one user listed.  Displays User name, Barcode, and Patron Group
  • Schedule (UXPROD-634)
    • Active, pending, etc. set automatically
    • Terms (Controlled vocabulary / Authorized value list) configured in settings
      •   - but can be overwritten
      • Start Date
      • End Date
  • Location (not Organization)
    • Prepopulate or change  temporary location (nice to have)
    • Location is associated with service point which is then used by patrons (discovery) and displayed to patron

    • Service points (UXPROD-640)?
  • Items  UXPROD-646


Regarding Organization/Service points - is this the location of items?  No document mentions "Organization" although it appears on the screen shots.  "Service points" and "Locations" are mentioned in some documentation but do not appear on the screen shots. 



What fields are go-live vs 'nice to have'?

What fields are mandatory/required?


Which fields should be repeatable (used for cross listing)?

What fields are used for inter-operability? - and by what systems?

What fields are missing?

Each section should be collapsible

Page Mockups