Skip to end of banner
Go to start of banner

Inventory app Version history

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Feature

UXPROD-4125 - Getting issue details... STATUS / UXPROD-4126 - Getting issue details... STATUS

Release

Sunflower

Document status

DRAFT

Overview

Action items

  1. Document business expectations? Where do we differ from Acquisitions? Some examples:

    1. ECS handling - change ownership

    2. Setting record for deletion

    3. Default display (sort, number to display, how to go through more history) - endless scroll? More?

  2. Document some user workflows (i.e. Single record overlay)

  3. Work with Kimie to revise UX ( )

    1. Remove “sort by”

    2. Remove examples where the app is identified as the trigger for the change

  4. Write user stories

In scope

Log that contains

  • User who made the change

  • Date time of change

  • Change made

  • Feature toggle

  • Applied to both FOLIO and MARC source instances

Out of scope

  • Ability to rollback to and/or view previous versions

  • Ability to sort

  • Including the app that triggered the change

  • Exporting version history

Tech design

Inventory Audit log

Requirements overview

Requirement

Notes

Jira(s)

1

Feature toggle so that libraries can set whether the feature is enabled (applies to both FOLIO and MARC source records)

  • ECS: This should probably be controlled by a central tenant feature flag?

2

Include version history on:

  • Instance detail view (fourth pane)

  • Holdings detail view

  • Items detail view

  • source view for MARC source records (second pane)

3

Display the date and time of the change in local timezone

4

Display the source of the change (user vs system)

5

Identify as a “Change”, and indicate whether the field was:

  • Added

  • Edited

  • Removed

6

Indicate the field changed on Instances detail view for both FOLIO and MARC source records.

Note: for MARC source records, the field changed should reflect the Instance field changed (see other requirement for Source view)

7

In Source view for MARC source records, identify the specific MARC fields (not to the point of indicators or subfields) changed

8

If a MARC field is changed that does NOT map to a FOLIO instance, do not include the change in the Instance detail view log

9

Record changes after the record has been opened (edited) for the first time

10

Ignore changes to metadata

11

Only include 15 changes in the log at a time

  • Maybe with a “+More” button and may require a message notifying user that it may take some time to load

12

Present a toast message that loading additional changes may take time

Questions

Question

Answer

Date

1

In the mockups, the user name is hyperlinked - does this just go to the user record?

2

Assuming that the highlight of fields changed (as implemented by Acquisitions) should be considered out of scope?

3

Do we indicate when one record is updated from changes to made to another record (such as updating the call number on a holdings record which then updates the effective call number on the item record)?

4

Do we include a change of “Shared” for ECS?

5

Do we include a change of “Derived”?

6

Do we include a change if the holdings ownership has changed in ECS?

7

Is keeping one year of history sufficient? Potentially need some sort of workflow where a user can make a call to some sort of archive to get more history?

8

Do we need to track when fields are reordered in quickMARC? I feel like no.

  • No labels