Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Modelinks-267: Extend authority mapping for quesnelia (do not merge!) #344

Open
wants to merge 5 commits into
base: release/v3.0
Choose a base branch
from
Open

Modelinks-267: Extend authority mapping for quesnelia (do not merge!) #344

wants to merge 5 commits into from

Conversation

elena-shmygaliova
Copy link
Collaborator

Purpose

Describe the purpose of this pull request. Why is this change necessary? What problem does it solve?

Approach

How does this change fulfill the purpose? Provide a high-level overview of the technical approach taken to address the problem.

Changes Checklist

  • API Changes: Document any API paths, methods, request or response bodies changed, added, or removed.
  • Database Schema Changes: Indicate any database schema changes and their impact. Confirm that migration scripts were created.
  • Interface Version Changes: Indicate any changes to interface versions.
  • Interface Dependencies: Document added or removed dependencies.
  • Permissions: Document any changes to permissions.
  • Logging: Confirm that logging is appropriately handled.
  • Unit Testing: Confirm that changed classes were covered by unit tests.
  • Integration Testing: Confirm that changed logic was covered by integration tests.
  • Manual Testing: Confirm that changes were tested on local or dev environment.
  • NEWS: Confirm that the NEWS file is updated with relevant information about the changes made in this pull request.

Related Issues

List any Jira issues related to this pull request.

Learning and Resources (if applicable)

Discuss any research conducted during the development of this pull request. Include links to relevant blog posts, patterns, libraries, or addons that were used to solve the problem.

Screenshots (if applicable)

If this pull request involves any visual changes or new features, consider including screenshots or GIFs to illustrate the changes.

mukhiddin-yusuf and others added 5 commits August 1, 2024 16:21
@mukhiddin-yusuf
fix(authority): Fix handling heading type change update event for aut…
0c55eb9 
…hority with linked instance

* fix(authority): Fix handling heading type change update event for authority with linked instance

- do not hard delete authority when handling heading type change update event

Closes: MODELINKS-242
(cherry picked from commit db93713)
@mukhiddin-yusuf
fix(authority): Fix handling update event for heading type change of …
0b66352 
…authority with linked instance (#306)

- do not hard delete authority when handling update event for heading type change

Closes: MODELINKS-242
(cherry picked from commit 3d52017)
@mukhiddin-yusuf
Update NEWS
9be1bb1
@mukhiddin-yusuf
[maven-release-plugin] prepare release v3.0.2
19c6a9b
@ShmElena
MODELINKS-267 Extend Authority fields
a951a5e
@elena-shmygaliova elena-shmygaliova requested a review from a team as a code owner October 28, 2024 17:04
@elena-shmygaliova elena-shmygaliova requested review from psmagin, viacheslavkol, mukhiddin-yusuf and SvitlanaKovalova1 and removed request for a team October 28, 2024 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@psmagin psmagin Awaiting requested review from psmagin psmagin is a code owner automatically assigned from folio-org/spitfire-backend

@viacheslavkol viacheslavkol Awaiting requested review from viacheslavkol viacheslavkol is a code owner automatically assigned from folio-org/spitfire-backend

@mukhiddin-yusuf mukhiddin-yusuf Awaiting requested review from mukhiddin-yusuf mukhiddin-yusuf is a code owner automatically assigned from folio-org/spitfire-backend

@SvitlanaKovalova1 SvitlanaKovalova1 Awaiting requested review from SvitlanaKovalova1 SvitlanaKovalova1 is a code owner automatically assigned from folio-org/spitfire-backend

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@elena-shmygaliova @mukhiddin-yusuf @ShmElena