[UIIN-1215] Holdings. Holdings statements notes. Public and Staff only. Created: 23/Jul/20  Updated: 14/Oct/20  Resolved: 24/Aug/20

Status: Closed
Project: ui-inventory
Components: None
Affects versions: None
Fix versions: 5.0.0

Type: Story Priority: P3
Reporter: Charlotte Whitt Assignee: Sergiy Sergiyenko
Resolution: Done Votes: 0
Labels: back-end, demo95, migration-load, migrations, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skärmavbild 2020-07-23 kl. 19.05.34.png     PNG File Skärmavbild 2020-07-23 kl. 20.43.10.png     PNG File Skärmavbild 2020-07-23 kl. 20.50.17.png     PNG File Skärmavbild 2020-07-23 kl. 21.36.28.png     PNG File Skärmavbild 2020-08-24 kl. 12.20.28.png     PNG File Skärmavbild 2020-08-24 kl. 12.22.15.png     PNG File Skärmavbild 2020-08-24 kl. 12.22.45.png    
Issue links:
Blocks
blocks UIDATIMP-642 Field mapping profile: Holdings: Add ... Closed
Defines
defines UXPROD-2450 Holdings record. Holdings statements ... Closed
Gantt End to Start
has to be done before MDEXP-231 Mapping profile - provide field name ... Closed
has to be done after MODINVSTOR-543 Holdings. Holdings statements notes. ... Closed
Relates
relates to UXPROD-559 Migrate Bibliographic & Holdings data Closed
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:


 Comments   
Comment by Charlotte Whitt [ 24/Aug/20 ]

Manual test in FOLIO Snapshot https://folio-snapshot.dev.folio.org/, version @folio/inventory 5.0.1000992, using Chrome.

All looks great, thank you so much Sergiy Sergiyenko

Ann-Marie Breaux, and Magda Zacharska - all three holdings statements notes have now been enhanced with the possibility to split the notes in public and staff only in Inventory. The work is not ready to be followed by updates in the Data Import MARC mapping and the Data Export MARC mapping. Thanks.

Comment by Marc Johnson [ 24/Aug/20 ]

Sergiy Sergiyenko Ryan Laddusaw

The pull request for MODINVSTOR-543 Closed has not been merged yet.

How is this working in folio-snapshot? Is it because the holdings statements objects defined in the JSON schema do not disallow additional properties and so the client is allowed to provide the new property even though it is yet to be defined?

cc: Zak Burke

Comment by Ann-Marie Breaux (Inactive) [ 24/Aug/20 ]

Hi Charlotte Whitt In your last sentence, you say the work is not ready to be followed by updates... did you mean the work is now ready? I'm guessing yes, but just wanted to doublecheck!

Comment by Magda Zacharska [ 24/Aug/20 ]

Ann-Marie Breaux - the backend work that is needed for data-export and data-import is not merged yet . That work is covered by MODINVSTOR-543 Closed .

Generated at Fri Feb 09 00:25:18 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.