Uploaded image for project: 'ui-inventory'
  1. ui-inventory
  2. UIIN-1215

Holdings. Holdings statements notes. Public and Staff only.

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Core: F - Sprint 95
    • Story Points:
      5
    • Development Team:
      Prokopovych

      Description

      Overview: When migrating data there is a need for University Chicago, Cornell, Duke and other libraries to have the possibility to mark holdings statement notes either as public notes or staff (non public) notes. This story is about relabeling an existing data element, and adding a new data element (detailed view and edit view)

      Use case:
      As a cataloger/technical staff I need to be able to distinct between holdings statements notes which is to be viewed only by staff (non public) or to be be displayed in e.g. the Discovery, or populated in ILL systems, so these holdings statements notes are to be marked as public notes.

      Stories:

      1. Story
        • Login to FOLIO Snapshot, go to Inventory
        • Go to ABA journal and view the holdings record: Main Library in detailed view.
        • Drill down to the Holdings details accordion
        • There are three different Holdings statements, and each of them have two data elements for notes (public, and staff). Each statement with notes is an array of strings. Each array is repeatable:
          • Holdings statement
            • Holdings statement public note - relabel the existing data element: Holdings statement note
            • Holdings statement staff note NEW (Repeatable, Not required)
          • Holdings statement for supplements
            • Holdings statement for supplements public note - relabel the existing data element: Holdings statement for supplements note
            • Holdings statement for supplements staff note NEW
          • Holdings statement for indexes
            • Holdings statement for indexes public note - relabel the existing data element: Holdings statement indexes note
            • Holdings statement for indexes staff note NEW
              See UX mock up:
      2. Story
        • Go to the edit view of the same holdings record
          • Holdings statement
            • Holdings statement public note - relabel the existing data element: Holdings statement note
            • Holdings statement staff note NEW (Repeatable, Not required)
          • Holdings statement for supplements
            • Holdings statement for supplements public note - relabel the existing data element: Holdings statement for supplements note
            • Holdings statement for supplements staff note NEW (Repeatable, Not required)
          • Holdings statement for indexes
            • Holdings statement for indexes public note - relabel the existing data element: Holdings statement indexes note
            • Holdings statement for indexes staff note NEW (Repeatable, Not required)

      Notes:

      1. This work has relevance for Data Import, Data Export, and Data Migration since the schema change will affect how data is mapped from incoming MARC Holdings, mapped to outgoing MARC holdings created on-the-fly, and existing holdings data that is being migrated into FOLIO. Data import and Data export will probably be dealing with this in Q4 2020. Similar timing is relevant for Duke and Chicago's data migration.
      2. UX-mock ups discussed with the MM-SIG 6/25/2020:
        https://docs.google.com/presentation/d/1NEmSyiBbEtRNPZiCQNjbv29bioXRRRToxY9R4qfrKZA/edit#slide=id.g80bbd261b6_0_62.
        At meeting 6/25/2020 the MM-SIG decided not to follow the general UX for notes as implemented for instance notes, holdings notes, and item notes.
      3. Christie Thomas Natascha Owens and Charlotte Whitt reviewed the different proposals 7/23/2020 and agreed upon:

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                SergiySergiyenko Sergiy Sergiyenko
                Reporter:
                charlotte Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases