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.

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

Show additional metadata in duplicates lists #60

Open
floriangantner opened this issue Dec 12, 2023 · 0 comments · May be fixed by #63
Open

Show additional metadata in duplicates lists #60

floriangantner opened this issue Dec 12, 2023 · 0 comments · May be fixed by #63
Labels

Comments

@floriangantner
Copy link

Is your feature request related to a problem? Please describe.
The duplicate detection has some configurable list of metadata to shown on matches during the import from external sources.

// NOTE: list of additional item metadata to show for duplicate match presentation list

These are passed through the listelement showing the duplicate.
https://github.com/4Science/dspace-angular/blob/4812f189b1bbdcfd890f45317635eb2f1e0bdb8d/src/app/shared/object-list/my-dspace-result-list-element/item-list-preview/item-list-preview.component.ts#L47C12-L47C24

, but the value is never read and it is not shown in the duplicates-list during import.

Describe the solution you'd like
We would like to show the values which determine the duplicate so some user can better reason why it is some duplicate.

The list of metadata could also be filtered by all matching metadatafields from the external source.

Describe alternatives or workarounds you've considered

Additional context

  • new duplicate list during import on DSpace-Cris 2023.02.00. before it was in the submission process
@atarix83 atarix83 added the bug label Dec 12, 2023
@floriangantner floriangantner linked a pull request Dec 13, 2023 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants