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

Associate service points with locations

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Analysis Estimate:
      XL < 15 days
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      Medium < 5 days
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      90
    • Rank: BNCF (MVP Feb 2020):
      R1
    • Rank: Chalmers (Impl Aut 2019):
      R1
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      From the wiki:

        • There can be 2 or more service points (e.g. circ desks) serving one physical location but most ILSes don't support this - there are work arounds for this, but would be great if FOLIO could make this possible (can a many to many relationship work without causing additional problems)
        • There can be 2 or more physical locations served by a single circ desk - this is very common and must be supported

        TestRail: Results

          Attachments

            Issue Links

            is blocked by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIORG-45 Location Hierarchy v1: Create Locations via JSON File

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-269 CRUD service points

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIORG-90 Assign Locations to Service Points

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-92 Check-in: Implications to item status

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

              Activity

                People

                Assignee:
                cboerema Cate Boerema
                Reporter:
                cboerema Cate Boerema
                Analysis Estimator:
                Cate Boerema Cate Boerema
                Front End Estimator:
                Jakub Skoczen Jakub Skoczen
                Back End Estimator:
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases