Skip to content

Conversation

@mhamann-ubl
Copy link
Contributor

@mhamann-ubl mhamann-ubl commented Nov 24, 2025

Purpose

This changes adds additionalCallNumbers to item and holding-records version history, as requested per: https://folio-org.atlassian.net/browse/UIIN-3558 and https://folio-org.atlassian.net/browse/UIIN-3559

Approach

Add a general additionalCallNumber object to the raml definition and extend item and holding-record to add a additionalCallNumbers array.

Pre-Merge Checklist:

Before merging this PR, please go through the following list and take appropriate actions.

  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • Were any API paths or methods changed, added or removed?
    • Were there any schema changes?
    • Did any of the interface versions change?
    • Were permissions changed, added, or removed?
    • Are there new interface dependencies?
    • There are no breaking changes in this PR.
    • Check logging

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do JIRAs exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all they appropriate links to blocked/related issues?
  • Are the JIRAs under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?

@mhamann-ubl mhamann-ubl requested a review from psmagin December 9, 2025 13:12
Copy link
Contributor

@psmagin psmagin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is a need to rename fields for additional call numbers. Having it without prefix is totaly fine.

@sonarqubecloud
Copy link

@mhamann-ubl
Copy link
Contributor Author

I don't think there is a need to rename fields for additional call numbers. Having it without prefix is totaly fine.

Alright. I did change it.

@elsenhans elsenhans merged commit 5cc2244 into master Dec 17, 2025
8 checks passed
@elsenhans elsenhans deleted the MODAUD-277-add-additionalCallNumbers-to-version-history branch December 17, 2025 13:59
elsenhans added a commit to folio-org/stripes-components that referenced this pull request Dec 22, 2025
# Description
These changes add the possibility to pass a customItemFormatter to the
AuditLogModal and add to this Formatter the collectionName.

# Why is this change necessary?
While adding additionalCallNumbers to the inventorys item history as
requested per this user story:
https://folio-org.atlassian.net/browse/UIIN-3540 we noticed, that
objects are currently being displayed as unordered, unnamed lists. This
seems to be deficient as the user has to guess which value belongs to
which property.

By adding a custom formatter, we are able to display these objects like
this:

<img width="2978" height="1269" alt="Screenshot from 2025-12-11
15-54-34"
src="https://github.com/user-attachments/assets/8ea804fd-6dcf-4dea-8825-c931c1b9b171"
/>

# Related changes

## Mod-Audit
folio-org/mod-audit#229

## UI-Inventory
folio-org/ui-inventory#2950

---------

Co-authored-by: elsenhans <elsenhans@users.noreply.github.com>
Co-authored-by: elsenhans <48911833+elsenhans@users.noreply.github.com>
github-actions bot pushed a commit to folio-org/stripes-components that referenced this pull request Dec 22, 2025
# Description
These changes add the possibility to pass a customItemFormatter to the
AuditLogModal and add to this Formatter the collectionName.

# Why is this change necessary?
While adding additionalCallNumbers to the inventorys item history as
requested per this user story:
https://folio-org.atlassian.net/browse/UIIN-3540 we noticed, that
objects are currently being displayed as unordered, unnamed lists. This
seems to be deficient as the user has to guess which value belongs to
which property.

By adding a custom formatter, we are able to display these objects like
this:

<img width="2978" height="1269" alt="Screenshot from 2025-12-11
15-54-34"
src="https://github.com/user-attachments/assets/8ea804fd-6dcf-4dea-8825-c931c1b9b171"
/>

# Related changes

## Mod-Audit
folio-org/mod-audit#229

## UI-Inventory
folio-org/ui-inventory#2950

---------

Co-authored-by: elsenhans <elsenhans@users.noreply.github.com>
Co-authored-by: elsenhans <48911833+elsenhans@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants