Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-622

CRUD basic course record

    XMLWordPrintable

    Details

    • Template:
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      XL < 15 days
    • Development Team:
      Thor
    • Calculated Total Rank:
      91
    • PO Rank:
      80.9
    • 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

      Create a new Course Record, Edit a course, and Delete a course one at a time.

      Library staff need the ability to create,edit and delete a descriptive listing of the Course information. The Course information contains sections of information that allow users, both in FOLIO and in linked systems to correctly discover the Course, and thereby see the list of associated items.

      The Course record should contain the following accordion sections with related descriptive fields, allow for the addition, editing and/or deleting of selected elements and include accordion functionality. expanding and contracting each section: (see also mockup with additional notes)
      FOLIO ID (unique identifier that is system created after the record is saved the first time) [not represented correctly in mockups]
      Course data (required) After creating the first course data record, users can create another course data set auto filled with information from the existing course data)

      • Course Name*
      • Department (Controlled vocabulary / Authorized value list - set in settings manage
      • Section
      • Course code/Number*

      Cross listing information (data that may be shared by several Courses)

      • Course Type % (Controlled vocabulary / Authorized value list - set in settings manager) The purpose of this field is to contain values such as “online”, “online/in person”, “in person”
      • Register ID (interoperability) % This is the registrar systems’s course unique course number. Also used for matching student data (copyright management), especially streaming video
      • External ID (interoperability) % 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 mechanismCross listed course link
        Used to indicate when the same course content has a different name, code, section and department

      ------ 2018 Course Reserve ------

      PO- Mock Ups located https://wiki.folio.org/x/L4Xc
      A course record should include the following:

      Course Data :

      Course Name
      Department
      Section
      Number
      Code
      Register ID
      Course Ware ID

      Y/N indicator for if the course is cross listed and if so all the fields above should be repeated as many times as needed (see mock up)

      Should have a taught by section that allows the user to look up users and allow for more than one user listed.

      A Folio Supplied ID number after saved.

      https://wiki.folio.org/x/L4Xc

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                kdrake Kelly Drake
                Reporter:
                Anya N. Arnold Anya Arnold
                Front End Estimator:
                Mike Taylor Mike Taylor
                Back End Estimator:
                Kurt Nordstrom Kurt Nordstrom
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases