Versions Compared

Version Old Version 33 New Version Current
Changes made by

Khalilah Gambrell

Christine Schultz-Richert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 be controlled by a central tenant feature flag

  • Should apply to all record types (in Inventory & MARC authority)

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

Ignore changes to metadata

10

Only include 15 changes cards in the log at a time in the instance history view

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

11

Present a toast message that loading additional changes may take time

12

Holdings & item deletion - Log in the audit

Questions

Question

Answer

Refinement Notes (1/9/24)

Answer Date

1

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

Yes

2

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

Yes

3

Do we indicate when one record is updated from changes 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)?

If there is a field that is autogenerated/updated, needs to be reflected in item version history

4

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

Yes. If a local record is shared, include a change of promoted to shared

  • Need to review with Folijet to think about if we need to move audit history to central tenant

  • Need more detailed requirements

5

Do we include a change of “Derived” and “Duplicate”?

Yes

  • Potentially not feasible: On backend, we do not specify whether it’s duplicated/derived, only that it is created *

*could be similar to effort of “via” line that we omitted

6

Do we include a change if

  • holdings ownership has changed in ECS

  • holdings moved to another instance

  • items moved to another holdings

Yes

  • Holdings ownership in ECS: Need to review with Folijet about implementation

  • Moving holdings/items: Will have change on backend; more of a question about how to show on UI

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?

Needs further discussion

  • For now there is no archiving capability included in design; configuration for retention period but not for archiving

  • Need to define what we mean by “archive” and if it’s really needed

8

Do we need to track when fields are reordered in quickMARC?

Yes - indicate field and a an action of “Moved”? - Ping acq about what they’re doing if:

  • there is a situation where data is reordered within the record?

  • there is a situation where record is moved?

9

Confirm whether there will be changes logged when records are linked together? (might show with parent/child?)

10

Confirm whether a tag added to holdings will be reflected in change log

11

Confirm whether the linking of authorities to bibs be reflected in change log

12

Do we need to implement this issue (

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODINVSTOR-1220
) as a part of UXPROD-4125 or UXPROD-4126?

Requires Kalibek Turgumbayev to review question.

13

What is the impact of implementing these issues https://folio-org.atlassian.net/browse/MODINVSTOR-1207 and https://folio-org.atlassian.net/browse/MODINVSTOR-1268 after UXPROD-4125 or UXPROD-4126?

Requires Kalibek Turgumbayev to review question.

14

Requirement for showing only 15 cards at one time (need UI requirements)

  • What if the entire card won’t fit on the screen, do we wrap or something else (collapsing, additional see more button?)

15

How do we show change history when the multiple fields are changed?

  • Need requirements:

    • If there are multiple contributors changed, do we have one line that contributor(s) were changed or multiple lines with each contributor

    • For inner fields of objects, how should we display these changes?

    • Do we append the index/order into the name of the field, like "contributors.0.xxx" or "contributors[0].xxx" when showing in the change history

16

Will we add the highlighted fields on the record in the future?

  • Could change current design

17

Will we add the rollback capability in the future?

  • Could change current design

18

Do we include bound-width changes?